On Sun, Oct 06, 2013 at 05:50:00PM +, brian m. carlson wrote:
On Sun, Oct 06, 2013 at 05:38:24PM +0200, Daniel Stenberg wrote:
On Sun, 6 Oct 2013, brian m. carlson wrote:
If there's a way to make Apache with mod_auth_kerb do that with
curl, then it doesn't require a change to git,
On Mon, Oct 07, 2013 at 08:02:41AM -0400, Jeff King wrote:
Yeah, instead we try to make two separate requests, and assume that the
first one clears the path for any further requests. Of course that
doesn't work for auth methods that actually negotiate for each request.
We should probably
On Sun, Oct 06, 2013 at 12:42:36AM +, brian m. carlson wrote:
GSS-Negotiate authentication always requires a rewind with CURL.
The remote in question only supports Negotiate authentication, so
prompting for a password in this case isn't going to help. I'm probably
going to look into
On Sun, 6 Oct 2013, Ilari Liusvaara wrote:
GSS-Negotiate authentication always requires a rewind with CURL.
Isn't 'Expect: 100-Continue' meant for stuff like this (not that it is
always supported properly)?
Yes it is and libcurl uses 100-Continue by default for that purpose. But the
harsh
On Sun, 6 Oct 2013, brian m. carlson wrote:
If there's a way to make Apache with mod_auth_kerb do that with curl, then
it doesn't require a change to git, and I'm happy to make it on my end.
But using the curl command line client, I don't see an Expect: 100-continue
anywhere during the
On Sun, Oct 06, 2013 at 05:38:24PM +0200, Daniel Stenberg wrote:
On Sun, 6 Oct 2013, brian m. carlson wrote:
If there's a way to make Apache with mod_auth_kerb do that with
curl, then it doesn't require a change to git, and I'm happy to
make it on my end. But using the curl command line
6 matches
Mail list logo
