From: Mike Hommey <mh@glandium.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Tay Ray Chuan <rctay89@gmail.com>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Yaroslav Halchenko <debian@onerussian.com>,
Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
Subject: Re: [PATCH] http/remote-curl: coddle picky servers
Date: Thu, 21 Jan 2010 17:07:07 +0100 [thread overview]
Message-ID: <20100121160707.GA31276@glandium.org> (raw)
In-Reply-To: <20100121155637.GA19078@spearce.org>
On Thu, Jan 21, 2010 at 07:56:37AM -0800, Shawn O. Pearce wrote:
> Tay Ray Chuan <rctay89@gmail.com> wrote:
> > When "info/refs" is a static file and not behind a CGI handler, some
> > servers may not handle a GET request for it with a query string
> > appended (eg. "?foo=bar") properly.
> >
> > If such a request fails, retry it sans the query string. In addition,
> > ensure that the "smart" http protocol is not used (a service has to be
> > specified with "?service=<service name>" to be conformant).
> >
> > Signed-off-by: Tay Ray Chuan <rctay89@gmail.com>
> > Reported-and-tested-by: Yaroslav Halchenko <debian@onerussian.com>
>
> *grumble* stupid Apache *grumble*
stupid Apache... configuration.
Check the error message you get on
http://git.debian.org/git/pkg-exppsy/pymvpa.git/info/refs?service=git-upload-pack:
The requested URL /gitweb.cgigit/pkg-exppsy/pymvpa.git/info/refs was not
found on this server.
Look closely at the start of the requested URL: /gitweb.cgi...
It comes from this rule:
RewriteCond %{QUERY_STRING} ^(.+)$
RewriteRule ^/(.*)$ /gitweb.cgi$1 [L,PT]
which is global to the virtual host.
Anyways, while git.debian.org can certainly be fixed for that, other
servers may want to do some different things with urls with parameters.
Mike
next prev parent reply other threads:[~2010-01-21 16:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 0:47 problem cloning via http since v1.6.6-rc0 Yaroslav Halchenko
2010-01-21 1:34 ` Tay Ray Chuan
2010-01-21 1:36 ` Tay Ray Chuan
2010-01-21 2:33 ` Yaroslav Halchenko
2010-01-21 4:01 ` Tay Ray Chuan
2010-01-21 4:38 ` Yaroslav Halchenko
2010-01-21 5:08 ` Ilari Liusvaara
2010-01-21 6:47 ` Tay Ray Chuan
2010-01-21 7:51 ` Tay Ray Chuan
2010-01-21 14:00 ` Yaroslav Halchenko
2010-01-21 14:41 ` [PATCH] http/remote-curl: coddle picky servers Tay Ray Chuan
2010-01-21 15:56 ` Shawn O. Pearce
2010-01-21 16:07 ` Mike Hommey [this message]
2010-01-21 16:10 ` git fetch -v not at all verbose? Michael S. Tsirkin
2010-01-21 16:18 ` Shawn O. Pearce
2010-01-21 16:35 ` Michael S. Tsirkin
2010-01-21 16:57 ` Shawn O. Pearce
2010-01-21 17:30 ` Michael S. Tsirkin
2010-01-21 17:47 ` Thomas Rast
2010-01-21 17:42 ` Junio C Hamano
2010-11-03 9:52 ` Michael S. Tsirkin
2010-11-03 16:14 ` Junio C Hamano
2010-01-21 16:20 ` [PATCH] http/remote-curl: coddle picky servers Tay Ray Chuan
2010-01-21 16:24 ` Shawn O. Pearce
2010-01-21 16:34 ` Mike Hommey
2010-01-21 16:34 ` Mike Hommey
2010-01-21 10:35 ` problem cloning via http since v1.6.6-rc0 Ilari Liusvaara
2010-01-21 11:36 ` Tay Ray Chuan
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=20100121160707.GA31276@glandium.org \
--to=mh@glandium.org \
--cc=debian@onerussian.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ilari.liusvaara@elisanet.fi \
--cc=rctay89@gmail.com \
--cc=spearce@spearce.org \
/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).