From: Andreas Schwab <schwab@linux-m68k.org>
To: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
Cc: Miles Bader <miles@gnu.org>, git@vger.kernel.org
Subject: Re: git "smart http" server vs. http redirects
Date: Sat, 18 Sep 2010 10:16:41 +0200 [thread overview]
Message-ID: <m262y3cvpy.fsf@whitebox.home> (raw)
In-Reply-To: <20100918070315.GA30872@LK-Perkele-V2.elisa-laajakaista.fi> (Ilari Liusvaara's message of "Sat, 18 Sep 2010 10:03:15 +0300")
Ilari Liusvaara <ilari.liusvaara@elisanet.fi> writes:
> On Sat, Sep 18, 2010 at 01:33:48PM +0900, Miles Bader wrote:
>
>> The savannah.gnu.org admins are trying out the git "smart http" server,
>> but it doesn't seem to handle http redirects properly... should it?
>> Is this a bug with the git server?
>>
>> The follow is from Sylvain Beucler;
>> > Hmmm, actually it works, but it doesn't support a HTTP redirect
>> > (namely git.sv.gnu.org -> git.savannah.gnu.org).
>> >
>> > $ git clone http://git.sv.gnu.org/r/freedink.git
>> > Initialized empty Git repository in /tmp/freedink/.git/
>> > error: RPC failed; result=22, HTTP code = 405
>
> 405 (Method not allowed)? Can you see what request it is trying to send
> and to where (the request that fails with 405 that is)?
I think this is a bug in the apache setup at savannnah. It is
responding to POST .../git-upload-pack with both 301 and 405. This does
not happen if you use the redirected address directly.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2010-09-18 8:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-18 4:33 git "smart http" server vs. http redirects Miles Bader
2010-09-18 7:03 ` Ilari Liusvaara
2010-09-18 8:16 ` Andreas Schwab [this message]
2010-09-18 8:47 ` [PATCH] smart-http: Don't change POST to GET when following redirect Andreas Schwab
2010-09-18 14:09 ` Miles Bader
2010-09-18 21:00 ` Jay Soffian
2010-09-24 6:20 ` [PATCH v2] " Tay Ray Chuan
2010-09-24 18:06 ` Andreas Schwab
2010-09-25 4:20 ` [PATCH v3] " 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=m262y3cvpy.fsf@whitebox.home \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=ilari.liusvaara@elisanet.fi \
--cc=miles@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.