From: Jakub Narebski <jnareb@gmail.com>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: git@vger.kernel.org, Petr Baudis <pasky@suse.cz>,
Junio C Hamano <gitster@pobox.com>,
Devin Doucette <devin@doucette.cc>
Subject: Re: [PATCH] gitweb: don't use pathinfo for global actions
Date: Tue, 6 Jan 2009 18:37:22 +0100 [thread overview]
Message-ID: <200901061837.23637.jnareb@gmail.com> (raw)
In-Reply-To: <1230896080-22801-1-git-send-email-giuseppe.bilotta@gmail.com>
On Fri, 2 Jan 2009, Giuseppe Bilotta wrote:
> With PATH_INFO urls, actions for the projects list (e.g. opml,
> project_index) were being put in the URL right after the base. The
> resulting URL is not properly parsed by gitweb itself, since it expects
> a project name as first component of the URL.
Therefore it really needs to be in, as df63fb also by Giuseppe
(gitweb: use href() when generating URLs in OPML) is already in,
and I think gitweb would generate broken OPML and TXT links without
this patch.
>
> Accepting global actions in use_pathinfo is not a very robust solution
> due to possible present and future conflicts between project names and
> global actions, therefore we just refuse to create PATH_INFO URLs when
> the project is not defined.
I think it is quite robust solution and it makes sense; we use
shortcuts http://git.example.com for projects_list page, and
http://git.example.com/path/to/repo.git for overview 'summary'
action for a project, therefore pathinfo has to look like the
following: http://git.example.com/repo/action/hash with "action"
_after_ "project". And there is also matter of backward compatibility
of URL (URLs shouldn't break).
Anyway, we have $home_link for default project_list page, which
is path_info without project, and query without query string...
>
> Signed-off-by: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Acked-by: Jakub Narebski <jnareb@gmail.com>
> ---
> gitweb/gitweb.perl | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
> index 99f71b4..fa7d8ad 100755
> --- a/gitweb/gitweb.perl
> +++ b/gitweb/gitweb.perl
> @@ -830,7 +830,7 @@ sub href (%) {
> }
>
> my $use_pathinfo = gitweb_check_feature('pathinfo');
> - if ($use_pathinfo) {
> + if ($use_pathinfo and defined $params{'project'}) {
> # try to put as many parameters as possible in PATH_INFO:
> # - project name
> # - action
> @@ -845,7 +845,7 @@ sub href (%) {
> $href =~ s,/$,,;
>
> # Then add the project name, if present
> - $href .= "/".esc_url($params{'project'}) if defined $params{'project'};
> + $href .= "/".esc_url($params{'project'});
> delete $params{'project'};
>
> # since we destructively absorb parameters, we keep this
Nice.
> --
> 1.5.6.5
>
>
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2009-01-06 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 11:34 [PATCH] gitweb: don't use pathinfo for global actions Giuseppe Bilotta
2009-01-06 17:37 ` Jakub Narebski [this message]
2009-01-07 21:19 ` Junio C Hamano
2009-01-07 21:32 ` Giuseppe Bilotta
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=200901061837.23637.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=devin@doucette.cc \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=giuseppe.bilotta@gmail.com \
--cc=pasky@suse.cz \
/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).