From: Scott Chacon <schacon@gmail.com>
To: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
Cc: Sitaram Chamarty <sitaramc@gmail.com>,
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 09:31:24 -0800 [thread overview]
Message-ID: <AANLkTikoGS4X8YbNgLT=Akx5RBj2d4Uybdx5QnJ+CWNo@mail.gmail.com> (raw)
In-Reply-To: <20101123161018.GB10420@LK-Perkele-V2.elisa-laajakaista.fi>
Hey,
On Tue, Nov 23, 2010 at 8:10 AM, Ilari Liusvaara
<ilari.liusvaara@elisanet.fi> wrote:
> Apparently pusher is falling back to dumb WebDAV push for some
> reason. And then failing because server does not support it
> or isn't configured apporiately for it.
Yes, the client will fall back to 'dumb' HTTP stuff if the server does
not respond properly to the initial /info/refs GET call. I believe
it's something like if the client asks for
/info/refs?service=git-upload-pack
and the server does not respond with the first line being:
# service=git-upload-pack
or the Content-Type header being:
application/x-git-upload-pack-advertisement
I believe either of those being absent will cause the client to think
that it's not a smart server, so it falls back to the DAV based push.
If you let us know what the curl output before that point was, or what
your apache config looks like, we might be able to help figure out
what's wrong with the server.
I got these DAV fallbacks all the time when my proxy wasn't letting
the /info/refs calls through to Apache properly.
Scott
next prev parent reply other threads:[~2010-11-23 17:31 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 [this message]
2010-11-23 19:40 ` Sitaram Chamarty
2010-11-23 19:50 ` Scott Chacon
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='AANLkTikoGS4X8YbNgLT=Akx5RBj2d4Uybdx5QnJ+CWNo@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).