Update docs

1 files changed, 0 insertions, 18 deletions

diff --git a/docs/en/cowboy/2.0/guide/broken_clients/index.html b/docs/en/cowboy/2.0/guide/broken_clients/index.html
index e05f85f5..41e8d59f 100644
--- a/docs/en/cowboy/2.0/guide/broken_clients/index.html
+++ b/docs/en/cowboy/2.0/guide/broken_clients/index.html
@@ -112,24 +112,6 @@ forking the project and editing the <code>cowboy_protocol</code> file
 directly.</p></div>

 </div>

 </div>

-<div class="sect1">

-<h2 id="_chunked_transfer_encoding">Chunked transfer-encoding</h2>

-<div class="sectionbody">

-<div class="paragraph"><p>Sometimes an HTTP client advertises itself as HTTP/1.1 but

-does not support chunked transfer-encoding. This is invalid

-behavior, as HTTP/1.1 clients are required to support it.</p></div>

-<div class="paragraph"><p>A simple workaround exists in these cases. By changing the

-Req object response state to <code>waiting_stream</code>, Cowboy will

-understand that it must use the identity transfer-encoding

-when replying, just like if it was an HTTP/1.0 client.</p></div>

-<div class="listingblock">

-<div class="content"><!-- Generator: GNU source-highlight 3.1.8

-by Lorenzo Bettini

-http://www.lorenzobettini.it

-http://www.gnu.org/software/src-highlite -->

-<pre><tt><span style="color: #009900">Req2</span> <span style="color: #990000">=</span> <span style="font-weight: bold"><span style="color: #000000">cowboy_req:set</span></span>(<span style="color: #FF6600">resp_state</span>, <span style="color: #FF6600">waiting_stream</span>)<span style="color: #990000">.</span></tt></pre></div></div>

-</div>

-</div>