Re: GSS-Negotiate authentication requires that all data fit into postbuffer
- From
- Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
- Date
- Oct 6, 2013, 10:50 UTC
- Message-ID
- <20131006105013.GA24950@LK-Perkele-VII>
- In-Reply-To
- <20131006004236.GB3460@vauxhall.crustytoothpaste.net>
On Sun, Oct 06, 2013 at 12:42:36AM +0000, brian m. carlson wrote:
Show 13 quoted lines
> > 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 this over the next couple of days, but two things > need to be done here: 1) do not prompt for a password if only Negotiate > authentication is requested, since it just won't work, and 2) recreate > the data as needed if we have to rewind, since otherwise pushing a fresh > copy of the Linux kernel repo simply isn't going to work as the buffer > will have to be too large. An alternative is to send a small amount of > data, smaller than the postbuffer, in the first chunk and only fail to > rewind if the second or subsequent chunks need rewinding.
Isn't 'Expect: 100-Continue' meant for stuff like this (not that it is always supported properly)?
-Ilari