doc: mention that proxies must be completely transparent
We already document in the FAQ that proxies must be completely transparent and not modify the request or response in any way, but add similar documentation to the http.proxy entry. We know that while the FAQ is very useful, users sometimes are less likely to read in favor of the documentation specific to an option or command, so adding it in both places will help users be adequately informed. Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
brian m. carlson committed
Jul 9, 2024 at 23:37 UTC
70405acf60ca20de1aaf0fe67440de93ee2318e6
1 file changed
+5
Documentation/config/http.txt
+5
@@ -7,6 +7,11 @@ http.proxy::
7
linkgit:gitcredentials[7] for more information. The syntax thus is
8
'[protocol://][user[:password]@]proxyhost[:port]'. This can be overridden
9
on a per-remote basis; see remote.<name>.proxy
10
++
11
+Any proxy, however configured, must be completely transparent and must not
12
+modify, transform, or buffer the request or response in any way. Proxies which
13
+are not completely transparent are known to cause various forms of breakage
14
+with Git.
15
16
http.proxyAuthMethod::
17
Set the method with which to authenticate against the HTTP proxy. This