On Sat, Dec 13, 2008 at 10:47 PM, Jakub Narebski <jnareb@xxxxxxxxx> wrote: > Matt McCutchen <matt@xxxxxxxxxxxxxxxxx> writes: > >> My Web site uses pathinfo mode and some rewrite magic to show the gitweb >> interface at the URL of the real repository directory (which users also >> pull from). In this case, it's desirable to end generated links to the >> project in a trailing slash so the Web server doesn't have to redirect >> the client to add the slash. This patch adds a second element to the >> "pathinfo" feature configuration to control the trailing slash. >> >> Signed-off-by: Matt McCutchen <matt@xxxxxxxxxxxxxxxxx> > > Did you check that it does not confuse gitweb if filename parameter is > passed using pathinfo? Gitweb used to rely on final '/' to > distinguish directory pathnames from ordinary pathnames, but I think > currently thanks to the fact that gitweb now embeds action in pathinfo > URL, and does not need to guess type, it is not an issue. > > Or only project URLs (i.e. only with project parameter, i.e. only > "http://git.example.com/project.git/"; but not other path_info links) > have trailing slash added? > > Errr... I see that it adds trailing slash only for project-only > path_info links, but the commit message was not entirely clear for me. If indeed the additional / is only asked for in summary view, I think there's no need for a feature toggle, we can always put it there. If not, I'm really curious about seeing the rewrite rules (they might also be worth adding to the gitweb documentation as examples of 'power usage'). -- Giuseppe "Oblomov" Bilotta -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
