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

Re: [PATCH v2 3/3] docs: mention when increasing http.postBuffer is valuable

From
Jeff King <peff@peff.net>
Date
Oct 17, 2019, 05:52 UTC
Message-ID
<20191017055254.GC10253@sigill.intra.peff.net>
In-Reply-To
<20191017005330.9021-4-sandals@crustytoothpaste.net>
On Thu, Oct 17, 2019 at 12:53:30AM +0000, brian m. carlson wrote:
Show 14 quoted lines
> Users in a wide variety of situations find themselves with HTTP push
> problems.  Oftentimes these issues are due to antivirus software,
> filtering proxies, or other man-in-the-middle situations; other times,
> they are due to simple unreliability of the network.
> 
> However, a common solution to HTTP push problems found online is to
> increase http.postBuffer.  This works for none of the aforementioned
> situations and is only useful in a small, highly restricted number of
> cases: essentially, when the connection does not properly support
> HTTP/1.1.
> 
> Document when raising this value is appropriate and what it actually
> does, and discourage people from using it as a general solution for push
> problems, since it is not effective there.

Yeah, I've run into some voodoo advice about this config option before. I think your advice neatly explains the situation.

-Peff
Previous: brian m. carlsonNext: brian m. carlson
Message 3 of 10 in “Documentation for common user misconceptions”
  1. 0/3 Documentation for common user misconceptionsbrian m. carlson, Oct 17, 2019
  2. 3/3 docs: mention when increasing http.postBuffer is valuablebrian m. carlson, Oct 17, 2019
  3. Jeff KingOct 17, 2019
  4. 2/3 doc: dissuade users from trying to ignore tracked filesbrian m. carlson, Oct 17, 2019
  5. Jeff KingOct 17, 2019
  6. 1/3 doc: provide guidance on user.name formatbrian m. carlson, Oct 17, 2019
  7. Jeff KingOct 17, 2019
  8. Junio C HamanoOct 17, 2019
  9. brian m. carlsonOct 17, 2019
  10. Jeff KingOct 18, 2019

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.