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 fc5ef96c701b9adddb75f454521f53c0afcbfe09..27eb221df7c47311d08a4148cbfbfb11710b89b6 100644 (file)
--- 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 2e31c12cb8437400ce4f59ac041ee2646e946dbc..d3705ed7eeb98077e72a2fcb0d64cd6af57ffe71 100644 (file)
--- a/src/SquidConfig.h
+++ b/src/SquidConfig.h
@@ -120,7 +120,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 2be97c4d73f94fff93cd7bb2b15cf7bf9fe4b4ac..1af3d4709b9ef80497e977241a819224f870b791 100644 (file)
--- a/src/cf.data.pre
+++ b/src/cf.data.pre
@@ -180,6 +180,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: ignore_expect_100
 TYPE: obsolete
 DOC_START
@@ -5256,33 +5262,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