From: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
To: Tay Ray Chuan <rctay89@gmail.com>
Cc: Yaroslav Halchenko <debian@onerussian.com>,
git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: problem cloning via http since v1.6.6-rc0
Date: Thu, 21 Jan 2010 12:35:01 +0200 [thread overview]
Message-ID: <20100121103500.GA19285@Knoppix> (raw)
In-Reply-To: <be6fef0d1001202247l7467a14ap8181eb3ed830167a@mail.gmail.com>
On Thu, Jan 21, 2010 at 02:47:37PM +0800, Tay Ray Chuan wrote:
> Hi,
>
> On Thu, Jan 21, 2010 at 1:08 PM, Ilari Liusvaara
> >
> > (i.e. webserver would ignore the query). This isn't true for git.debian.org.
> > Requesting the latter works (and the data formatting looks sane), but the
> > former is 404. This causes the fetch to fail.
>
> afaik, putting a "?var1=val1&var2=...." still makes it a normal GET
> request, even if the url requested is just a plain file and not some
> cgi handler that uses those variables/values.
Yes, it is normal GET (POST would be something else). And wheither it is CGI
doesn't come into play for request since client decides wheither to send GET
or POST and wheither to include query or not.
Query is just technical name for part between ? and # (or end of HTTP URL),
and can be present in any type of request that accepts http:// URL.
As said, code expects query part to be ignored if target is regular file
but broke when it didn't get ignored.
-Ilari
next prev parent reply other threads:[~2010-01-21 10:35 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
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 ` Ilari Liusvaara [this message]
2010-01-21 11:36 ` problem cloning via http since v1.6.6-rc0 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=20100121103500.GA19285@Knoppix \
--to=ilari.liusvaara@elisanet.fi \
--cc=debian@onerussian.com \
--cc=git@vger.kernel.org \
--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).