From: Tay Ray Chuan <rctay89@gmail.com>
To: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
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 19:36:51 +0800 [thread overview]
Message-ID: <be6fef0d1001210336i56605a37tfbede92cab794d76@mail.gmail.com> (raw)
In-Reply-To: <20100121103500.GA19285@Knoppix>
Hi,
On Thu, Jan 21, 2010 at 6:35 PM, Ilari Liusvaara
<ilari.liusvaara@elisanet.fi> wrote:
> 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.
yes, indeed, I misread your message. Your idea of the query string
affecting the server response didn't strike me then.
--
Cheers,
Ray Chuan
prev parent reply other threads:[~2010-01-21 11:36 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 ` problem cloning via http since v1.6.6-rc0 Ilari Liusvaara
2010-01-21 11:36 ` Tay Ray Chuan [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=be6fef0d1001210336i56605a37tfbede92cab794d76@mail.gmail.com \
--to=rctay89@gmail.com \
--cc=debian@onerussian.com \
--cc=git@vger.kernel.org \
--cc=ilari.liusvaara@elisanet.fi \
--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).