Re: disabling PROPFIND when using smart http

From: Scott Chacon <schacon@gmail.com>
Date: Nov 23, 2010, 19:50 UTC
Message-ID: <AANLkTikmAGd4Dyv7LijbnKX5Wywzf=zRX2Kpv+6MUZtu@mail.gmail.com>
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:

Show 6 quoted lines

>
> 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