Re: [PATCHv6 3/5] gitweb: use_pathinfo filenames start with /
- From
Jakub Narebski <jnareb@gmail.com>
- Date
- Oct 19, 2008, 08:43 UTC
- Message-ID
- <200810191043.16395.jnareb@gmail.com>
- In-Reply-To
- <cb7bb73a0810181657i67d6b9f8o66db9f57bcf01dd3@mail.gmail.com>
On Sun, 19 Oct 2008, Giuseppe Bilotta wrote:
Show 7 quoted lines
> On Sun, Oct 19, 2008 at 1:26 AM, Jakub Narebski <jnareb@gmail.com> wrote:
>> On Thu, 16 Oct 2008, Giuseppe Bilotta wrote:
>>
>>> When using path info, make filenames start with a / (right after the :
>>> that separates them from the hash base). This minimal change allows
>>> relative navigation to work properly when viewing HTML files in raw
>>> ('blob_plain') mode.[...]
Show 12 quoted lines
>> For example for http://repo.or.cz/w/git.git/html:/git.html links leads >> to correct HTML pages, while for http://repo.or.cz/w/git.git/html:git.html >> they lead to empty gitweb page (no errors, so link checker would be >> fooled). > > An idea that could be taken into consideration, if the ability to > navigate web documents is deemed of primary importance, would be a > redirect from the no-slash URL (a hand-coded one, given that with this > patch we only generate slashed URLs) to the slashed URL. Not sure it's > worth the effort (and reparsing) though: it would obviously be MUCH > nicer if we could change the URL without having to actually reload the > document ...
I think that changing URL without reloading is impossible because of security reasons. For example if you change document.location in JavaScript changing the URL (you can add links to non-existing anchors without reloading) then web browser reloads the page from new URL.
What you can do is early redirect using 301 Moved Permanently (or similar) and Location: redirect, using $cgi->redirect() like in git_object().
Also not sure if it is worth the effort...
-- Jakub Narebski Poland