git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "José María Escartín Esteban" <ripero84@gmail.com>
To: git@vger.kernel.org
Cc: Jakub Narebski <jnareb@gmail.com>
Subject: Static gitweb content when using pathinfo
Date: Thu, 05 Apr 2012 15:54:27 +0200	[thread overview]
Message-ID: <4F7DA413.2020502@gmail.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I'm running gitweb in a server.example.com/gitweb/ scenario.  If I don't enable
pathinfo everything works fine, but when I enable pathinfo the static content
stops showing up in the browser.

I'm not an HTML or perl expert, but I think that this may be due to a missing
slash in the construction of the base tag:  Using the upstream script I am getting

<base href="http://server.example.com/gitweb" />

and no static content.  Once I tune the script to add a final slash to the url

<base href="http://server.example.com/gitweb/" />

the static content shows up again.

Maybe I'm doing something wrong (am I?), and possibly this can be solved from
the web server side, but maybe it also makes some sense to include in the script
some check that the url used in the base tag ends with a slash.  In that case,
given my lack of perl skills, I would be really grateful if somebody implemented it.

Thank you for your attention.

Greetings,

	E.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk99pBMACgkQY+7weQMem3y28wCeOotCIgFF8sT4LKgq599IhB/E
0qcAn2dri0Z61PjV90bxfBG1QMFD3c75
=6PBz
-----END PGP SIGNATURE-----

             reply	other threads:[~2012-04-05 13:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05 13:54 José María Escartín Esteban [this message]
2012-04-05 21:14 ` Static gitweb content when using pathinfo Jakub Narebski
2012-04-14 17:19   ` Jakub Narebski
2012-04-16 15:18     ` José María Escartín Esteban
2012-04-17 12:30       ` Jakub Narebski
2012-04-24  7:01         ` José María Escartín Esteban

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F7DA413.2020502@gmail.com \
    --to=ripero84@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).