From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: [BUG] remote curl fetches HTML documents
Date: Wed, 31 Mar 2010 01:36:21 +0530 [thread overview]
Message-ID: <f3271551003301306i7e7659acu4724fc9e5a575468@mail.gmail.com> (raw)
Hi,
I found a bug in the curl family of remote helpers. I've posted a
bugfix by assuming as little about the URL that libcurl accepts as
possible.
$ git remote-http foo
list
0000000000000000000000000000000000000000 html>
0000000000000000000000000000000000000000 <head>
0000000000000000000000000000000000000000 <title>OpenDNS</title>
0000000000000000000000000000000000000000 </head>
0000000000000000000000000000000000000000 </head>
0000000000000000000000000000000000000000 <body id="mainbody"
onLoad="testforbanner();" style="margin: 0px;">
<SNIP>
$ git remote-http foo
fetch 0000000000000000000000000000000000000000 html>
error: inflate: data stream error (incorrect header check)
error: File 0000000000000000000000000000000000000000
(foo/objects/00/00000000000000000000000000000000000000) corrupt
error: Unable to find 0000000000000000000000000000000000000000 under foo
Cannot obtain needed object 0000000000000000000000000000000000000000
error: Fetch failed.
-- Ram
reply other threads:[~2010-03-30 20:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f3271551003301306i7e7659acu4724fc9e5a575468@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=git@vger.kernel.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).