Skip to content

Commit

Permalink
doc: mention that proxies must be completely transparent
Browse files Browse the repository at this point in the history
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>
  • Loading branch information
bk2204 authored and gitster committed Jul 10, 2024
1 parent 804ecbc commit 70405ac
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions Documentation/config/http.txt
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,11 @@ http.proxy::
linkgit:gitcredentials[7] for more information. The syntax thus is
'[protocol://][user[:password]@]proxyhost[:port]'. This can be overridden
on a per-remote basis; see remote.<name>.proxy
+
Any proxy, however configured, must be completely transparent and must not
modify, transform, or buffer the request or response in any way. Proxies which
are not completely transparent are known to cause various forms of breakage
with Git.

http.proxyAuthMethod::
Set the method with which to authenticate against the HTTP proxy. This
Expand Down

0 comments on commit 70405ac

Please sign in to comment.