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
brian m. carlson <sandals@crustytoothpaste.net>
Date
Oct 6, 2013, 15:29 UTC
Message-ID
<20131006152908.GD3460@vauxhall.crustytoothpaste.net>
In-Reply-To
<alpine.DEB.2.00.1310061658330.6366@tvnag.unkk.fr>
On Sun, Oct 06, 2013 at 05:00:02PM +0200, Daniel Stenberg wrote:
Show 11 quoted lines
> 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.

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 connection using Debian's curl 7.32.0-1. Do I need to send a certain amount of data to see that behavior?

The command line I used was
  curl -v -d '0000' -H'Transfer-Encoding: chunked' -H'Content-Type: application/x-git-receive-pack-request' --negotiate -u bmc: https://git.crustytoothpaste.net/git/bmc/test.git/git-receive-pack
-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
Previous: Daniel StenbergNext: Daniel Stenberg
Message 4 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.