undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

gitweb: make static files accessible with PATH_INFO

Browse Source 
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>
This commit is contained in:
Giuseppe Bilotta 2009-01-31 02:31:50 +01:00 committed by Junio C Hamano
parent 499cc56a60
commit c3254aeecf
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gitweb/gitweb.perl
View File

@ -2901,6 +2901,11 @@ sub git_header_html {
<meta name="robots" content="index, nofollow"/> <meta name="robots" content="index, nofollow"/>
<title>$title</title> <title>$title</title>
EOF EOF
# the stylesheet, favicon etc urls won't work correctly with path_info unless we
# set the appropriate base URL
if ($ENV{'PATH_INFO'}) {
print '<base href="'.esc_url($my_url).'" />\n';
}
# print out each stylesheet that exist # print out each stylesheet that exist
if (defined $stylesheet) { if (defined $stylesheet) {
#provides backwards capability for those people who define style sheet in a config file #provides backwards capability for those people who define style sheet in a config file