From: Jeff King <peff@peff.net>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v2 3/3] docs: mention when increasing http.postBuffer is valuable
Date: Thu, 17 Oct 2019 01:52:55 -0400 [thread overview]
Message-ID: <20191017055254.GC10253@sigill.intra.peff.net> (raw)
In-Reply-To: <20191017005330.9021-4-sandals@crustytoothpaste.net>
On Thu, Oct 17, 2019 at 12:53:30AM +0000, brian m. carlson wrote:
> 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
prev parent reply other threads:[~2019-10-17 5:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 0:53 [PATCH v2 0/3] Documentation for common user misconceptions brian m. carlson
2019-10-17 0:53 ` [PATCH v2 1/3] doc: provide guidance on user.name format brian m. carlson
2019-10-17 5:40 ` Jeff King
2019-10-17 7:39 ` Junio C Hamano
2019-10-17 22:20 ` brian m. carlson
2019-10-18 5:37 ` Jeff King
2019-10-17 0:53 ` [PATCH v2 2/3] doc: dissuade users from trying to ignore tracked files brian m. carlson
2019-10-17 5:44 ` Jeff King
2019-10-17 0:53 ` [PATCH v2 3/3] docs: mention when increasing http.postBuffer is valuable brian m. carlson
2019-10-17 5:52 ` Jeff King [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191017055254.GC10253@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sandals@crustytoothpaste.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).