Explain the reason for and behavior of the new http.continue option, and that it
is enabled by default. Furthermore, explain that it is required for large
GSS-Negotiate requests but incompatible with some proxies.
Signed-off-by: brian m. carlson <sand...@crustytoothpaste.net>
---
Documentation/config.txt | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/Documentation/config.txt b/Documentation/config.txt
index fca7749..5fff2b2 100644
--- 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 enabled.
+
http.lowSpeedLimit, http.lowSpeedTime::
If the HTTP transfer speed is less than 'http.lowSpeedLimit'
for longer than 'http.lowSpeedTime' seconds, the transfer is aborted.
--
1.8.4.rc3
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
