Re: [PATCHv6 3/5] gitweb: use_pathinfo filenames start with /
- From
Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
- Date
- Oct 18, 2008, 23:57 UTC
- Message-ID
- <cb7bb73a0810181657i67d6b9f8o66db9f57bcf01dd3@mail.gmail.com>
- In-Reply-To
- <200810190126.06697.jnareb@gmail.com>
On Sun, Oct 19, 2008 at 1:26 AM, Jakub Narebski <jnareb@gmail.com> wrote:
Show 9 quoted lines
> 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.
>
> This means generating project/action/hash_base:/filename rather than
> earlier project/action/hash_base:filename, isn't it?Exactly. We _accept_ paths with or without the /, but we always generate paths with it.
> 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 ...
-- Giuseppe "Oblomov" Bilotta