| commit | c3254aeecf89a620db262480a7c424e7607f1e2a | |
| author | Giuseppe Bilotta <giuseppe.bilotta@gmail.com> | |
| Sat, 31 Jan 2009 01:31:50 +0000 (31 02:31 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Sat, 31 Jan 2009 05:08:24 +0000 (30 21:08 -0800) | ||
| tree | a3b39f2c80534328d9b0d2e93cdeeba435f80300 | treesnapshot (tar.gz zip) |
| parent | 499cc56a60b5c90415c74857035579713a07fa1b | commitdiff |
gitweb: make static files accessible with PATH_INFO
Gitweb links to a number of static files such as CSS stylesheets,
favicon or the git logo. When, such as with the default Makefile, the
paths to these files are relative (i.e. doesn't start with a "/"), the
files become inaccessible in any view other tha project list and summary
page if gitweb is invoked with a non-empty PATH_INFO.
Fix this by adding a <base> element pointing to the script's own URL,
which ensure that all relative paths will be resolved correctly.
Signed-off-by: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Acked-by: Jakub Narebski <jnareb@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Gitweb links to a number of static files such as CSS stylesheets,
favicon or the git logo. When, such as with the default Makefile, the
paths to these files are relative (i.e. doesn't start with a "/"), the
files become inaccessible in any view other tha project list and summary
page if gitweb is invoked with a non-empty PATH_INFO.
Fix this by adding a <base> element pointing to the script's own URL,
which ensure that all relative paths will be resolved correctly.
Signed-off-by: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Acked-by: Jakub Narebski <jnareb@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| gitweb/gitweb.perl | diffblobblamehistory |