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
Jonathan Nieder <jrnieder@gmail.com>
Date
Oct 11, 2013, 23:50 UTC
Message-ID
<20131011235052.GV9464@google.com>
In-Reply-To
<1381530945-90590-3-git-send-email-sandals@crustytoothpaste.net>
brian m. carlson wrote:
Show 14 quoted lines
> --- a/Documentation/config.txt
> +++ b/Documentation/config.txt
> @@ -1516,6 +1516,15 @@ http.postBuffer::
>  	massive pack file locally.  Default is 1 MiB, which is
>  	sufficient for most requests.
>  
> +http.continue::
> +	Ensure that authentication succeeds before sending the pack data when
> +	POSTing data using the smart HTTP transport.  This is done by
> +	requesting a 100 Continue response.  For requests larger than
> +	'http.postBuffer', this is required when using GSS-Negotiate
> +	(Kerberos) authentication over HTTP.  However, some proxies do not
> +	handle the protocol exchange gracefully; for them, this option must be
> +	disabled.  Defaults to disabled.

It's not only your company's proxy that might mishandle 100-continue but the target server's reverse proxy (or from the point of view of the user, the target server), right?

I think the wording could be clearer about the impact of the setting ("some proxies and reverse proxies" or something).

Perhaps this should be conditional on the authentication method used, so affected people could still contact broken servers without having different configuration per server and without having to wait a second for the timeout.

Thanks, Jonathan

Previous: brian m. carlsonNext: brian m. carlson
Message 6 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.