From: Amos Jeffries <squid3@treenet.co.nz>
Date: Sat, 24 Jan 2015 04:25:44 +0000 (-0800)
Subject: Docs: drop obsolete chunked_request_body_max_size references
X-Git-Tag: merge-candidate-3-v1~318
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=16cd62b7c0949d5bc17682b2624d8186b5012296;p=thirdparty%2Fsquid.git

Docs: drop obsolete chunked_request_body_max_size references

This option has done nothing since Squid-3.2.
---

diff --git a/doc/release-notes/release-3.2.sgml b/doc/release-notes/release-3.2.sgml
index c336456983..c0fffa4de0 100644
--- a/doc/release-notes/release-3.2.sgml
+++ b/doc/release-notes/release-3.2.sgml
@@ -744,6 +744,9 @@ This section gives a thorough account of those changes in three categories:
 <sect1>Removed tags<label id="removedtags">
 <p>
 <descrip>
+	<tag>chunked_request_body_max_size</tag>
+	<p>Obsolete. Squid is now HTTP/1.1 with support for streaming chunked encoded requests.
+
 	<tag>dns_v4_fallback</tag>
 	<p>Obsolete. Replaced by DNS parallel lookups.
 
diff --git a/src/SquidConfig.h b/src/SquidConfig.h
index 6d10bc51b3..c001348dde 100644
--- a/src/SquidConfig.h
+++ b/src/SquidConfig.h
@@ -103,7 +103,6 @@ public:
     } Timeout;
     size_t maxRequestHeaderSize;
     int64_t maxRequestBodySize;
-    int64_t maxChunkedRequestBodySize;
     size_t maxRequestBufferSize;
     size_t maxReplyHeaderSize;
     AclSizeLimit *ReplyBodySize;
diff --git a/src/cf.data.pre b/src/cf.data.pre
index 221559ce4e..b780dd11c4 100644
--- a/src/cf.data.pre
+++ b/src/cf.data.pre
@@ -175,6 +175,12 @@ DOC_START
 DOC_END
 
 # Options Removed in 3.2
+NAME: chunked_request_body_max_size
+TYPE: obsolete
+DOC_START
+	Remove this line. Squid is now HTTP/1.1 compliant.
+DOC_END
+
 NAME: dns_v4_fallback
 TYPE: obsolete
 DOC_START
@@ -5673,33 +5679,6 @@ DOC_START
 	a large file.
 DOC_END
 
-NAME: chunked_request_body_max_size
-COMMENT: (bytes)
-TYPE: b_int64_t
-DEFAULT: 64 KB
-LOC: Config.maxChunkedRequestBodySize
-DOC_START
-	A broken or confused HTTP/1.1 client may send a chunked HTTP
-	request to Squid. Squid does not have full support for that
-	feature yet. To cope with such requests, Squid buffers the
-	entire request and then dechunks request body to create a
-	plain HTTP/1.0 request with a known content length. The plain
-	request is then used by the rest of Squid code as usual.
-
-	The option value specifies the maximum size of the buffer used
-	to hold the request before the conversion. If the chunked
-	request size exceeds the specified limit, the conversion
-	fails, and the client receives an "unsupported request" error,
-	as if dechunking was disabled.
-
-	Dechunking is enabled by default. To disable conversion of
-	chunked requests, set the maximum to zero.
-
-	Request dechunking feature and this option in particular are a
-	temporary hack. When chunking requests and responses are fully
-	supported, there will be no need to buffer a chunked request.
-DOC_END
-
 NAME: broken_posts
 IFDEF: USE_HTTP_VIOLATIONS
 TYPE: acl_access