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

Re: [PATCH v2 2/2] Update documentation for http.continue option

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Oct 23, 2013, 22:56 UTC
Message-ID
<20131023225632.GZ865149@vauxhall.crustytoothpaste.net>
In-Reply-To
<CAJo=hJssxNtJSeLgwG5nON=Y-7HzZPULiwzH+0SXeU8tp3FC-A@mail.gmail.com>
On Tue, Oct 22, 2013 at 08:21:48PM -0700, Shawn Pearce wrote:
Show 5 quoted lines
> From my perspective, it is OK to defaulting to use 100-continue if the
> server supports Negotiate. If the user is stuck behind a broken proxy
> and can't authenticate, they can't authenticate. They can either set
> the variable to false, or fix their proxy, or use a different server,
> etc.

I think Jonathan's suggestion was to get rid of the variable altogether and simply make the code conditional on whether the server is offering GSS-Negotiate. I plan to make the use of 100-continue conditional on large_request as well, so that it only covers the case where it would otherwise fail. People who have broken proxies or broken servers and are using GSS-Negotiate (which, as I said, is probably very few people, if any) will simply have to increase the postbuffer size as before.

-- 
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: Shawn PearceNext: Jeff King
Message 14 of 18 in “HTTP GSS-Negotiate improvements”
  1. 0/2 HTTP GSS-Negotiate improvementsbrian m. carlson, Oct 11, 2013
  2. 1/2 http: add option to enable 100 Continue responsesbrian m. carlson, Oct 11, 2013
  3. Jonathan NiederOct 11, 2013
  4. brian m. carlsonOct 12, 2013
  5. 2/2 Update documentation for http.continue optionbrian m. carlson, Oct 11, 2013
  6. Jonathan NiederOct 11, 2013
  7. brian m. carlsonOct 12, 2013
  8. brian m. carlsonOct 18, 2013
  9. Junio C HamanoOct 22, 2013
  10. Jonathan NiederOct 22, 2013
  11. Jonathan NiederOct 23, 2013
  12. brian m. carlsonOct 23, 2013
  13. Shawn PearceOct 23, 2013
  14. brian m. carlsonOct 23, 2013
  15. Jeff KingOct 25, 2013
  16. brian m. carlsonOct 25, 2013
  17. Junio C HamanoOct 23, 2013
  18. brian m. carlsonOct 23, 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.