From: Radoslaw Szkodzinski <astralstorm@o2.pl>
To: Nick Hengeveld <nickh@reactrix.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [BUG] git-http-fetch segfault
Date: Tue, 04 Apr 2006 22:25:26 +0200 [thread overview]
Message-ID: <4432D636.4050407@o2.pl> (raw)
In-Reply-To: <20060404184935.GG14967@reactrix.com>
[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]
Nick Hengeveld wrote:
> On Tue, Apr 04, 2006 at 07:11:40PM +0200, Radoslaw Szkodzinski wrote:
>
>> I have some problems cloning stgit repository (maybe something's broken there).
>>
>> astralstorm@zen /home/devel $ git clone
>> http://homepage.ntlworld.com/cmarinas/stgit.git stgit
>> error: Unable to find adad46f365219e9bcc1a212826ca65eaac09729c under
>> http://homepage.ntlworld.com/cmarinas/stgit.git/
>> Cannot obtain needed blob adad46f365219e9bcc1a212826ca65eaac09729c
>> while processing commit 8847a11b3bbf5406f37a360e5466f0e392c56383.
>
> That host name resolves to multiple IP addresses, is it possible that
> one of the servers was out of sync? I tried cloning directly from each
> address and couldn't reproduce the problem.
>
Okay, I've nailed it. It's caused by Privoxy.
It seems that Privoxy sends its 404 page with 200 OK reply.
Clearly a broken response.
Does anyone have any better proxy supporting real SOCKS 4a/5 upstream proxy?
(for Tor)
Delegate doesn't count - it has broken HTTP code, 1.0 only and slow too.
--
GPG Key id: 0xD1F10BA2
Fingerprint: 96E2 304A B9C4 949A 10A0 9105 9543 0453 D1F1 0BA2
AstralStorm
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
prev parent reply other threads:[~2006-04-04 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 17:11 [BUG] git-http-fetch segfault Radoslaw Szkodzinski
2006-04-04 18:49 ` Nick Hengeveld
2006-04-04 19:54 ` Radoslaw Szkodzinski
2006-04-04 20:25 ` Radoslaw Szkodzinski [this message]
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=4432D636.4050407@o2.pl \
--to=astralstorm@o2.pl \
--cc=git@vger.kernel.org \
--cc=nickh@reactrix.com \
/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.