git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: GSS-Negotiate authentication requires that all data fit into postbuffer

From
Daniel Stenberg <daniel@haxx.se>
Date
Oct 6, 2013, 15:00 UTC
Message-ID
<alpine.DEB.2.00.1310061658330.6366@tvnag.unkk.fr>
In-Reply-To
<20131006105013.GA24950@LK-Perkele-VII>
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 reality is that lots of (most?) servers just don't care and aren't setup to respond properly and instead we end up having to send data multiple times in vain.

-- 
  / daniel.haxx.se
Previous: Ilari LiusvaaraNext: brian m. carlson
Message 3 of 8 in “GSS-Negotiate authentication requires that all data fit into postbuffer”
  1. brian m. carlsonOct 6, 2013
  2. Ilari LiusvaaraOct 6, 2013
  3. Daniel StenbergOct 6, 2013
  4. brian m. carlsonOct 6, 2013
  5. Daniel StenbergOct 6, 2013
  6. brian m. carlsonOct 6, 2013
  7. Jeff KingOct 7, 2013
  8. brian m. carlsonOct 7, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.