From: Scott Chacon <schacon@gmail.com>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>,
Git Mailing List <git@vger.kernel.org>,
"Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: disabling PROPFIND when using smart http
Date: Tue, 23 Nov 2010 11:50:56 -0800 [thread overview]
Message-ID: <AANLkTikmAGd4Dyv7LijbnKX5Wywzf=zRX2Kpv+6MUZtu@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimvKg3mwfZUoRHoj=uW0FxGS=meF-ChLJKEtHcp@mail.gmail.com>
Hey,
On Tue, Nov 23, 2010 at 11:40 AM, Sitaram Chamarty <sitaramc@gmail.com> wrote:
>
> Well it was someone else, but the pastie he has sent was
> http://pastebin.com/eaB0G1gx -- which may or may not help, because it
> doesn't seem to show the response *body*, only the headers.
>
> If that doesn't help I'll try and reproduce the problem myself first.
Still, it's enough. The request is obviously not getting back to the
Git CGI for some reason. There are a number of headers that should
have been returned after the first authed GET to /info/refs (lines
35-42 have the servers response). It should have:
< Content-Type: application/x-git-receive-pack-advertisement
< Pragma: no-cache
< Cache-Control: no-cache, max-age=0, must-revalidate
The Git CGI will set all of those. Since it's not, and it's setting
things like ETags, it's not the Git CGI you're communicating with.
Check the apache logs and see why it's not routing the request to the
cgi.
Scott
prev parent reply other threads:[~2010-11-23 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 15:40 disabling PROPFIND when using smart http Sitaram Chamarty
2010-11-23 16:10 ` Ilari Liusvaara
2010-11-23 17:31 ` Scott Chacon
2010-11-23 19:40 ` Sitaram Chamarty
2010-11-23 19:50 ` Scott Chacon [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='AANLkTikmAGd4Dyv7LijbnKX5Wywzf=zRX2Kpv+6MUZtu@mail.gmail.com' \
--to=schacon@gmail.com \
--cc=git@vger.kernel.org \
--cc=ilari.liusvaara@elisanet.fi \
--cc=sitaramc@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).