comparison xml/en/docs/faq/chunked_encoding_from_backend.xml @ 1923:66a30a380fba

Fixed links to tools.ietf.org.
author Ruslan Ermilov <ru@nginx.com>
date Mon, 06 Mar 2017 16:02:23 +0300
parents af3f38e349eb
children 4add6ae1296f
comparison
equal deleted inserted replaced
1922:94493c0ff5f6 1923:66a30a380fba
6 6
7 <article name="Why nginx doesn’t handle chunked encoding 7 <article name="Why nginx doesn’t handle chunked encoding
8 responses from my backend properly?" 8 responses from my backend properly?"
9 link="/en/docs/faq/chunked_encoding_from_backend.html" 9 link="/en/docs/faq/chunked_encoding_from_backend.html"
10 lang="en" 10 lang="en"
11 rev="1"> 11 rev="2">
12 12
13 <section> 13 <section>
14 14
15 <para> 15 <para>
16 <initial>Q:</initial> 16 <initial>Q:</initial>
33 </para> 33 </para>
34 34
35 <para> 35 <para>
36 <initial>A:</initial> 36 <initial>A:</initial>
37 Your backend violates HTTP specification (see 37 Your backend violates HTTP specification (see
38 <link url="http://tools.ietf.org/html/rfc2616#section-3.6">RFC 2616, 38 <link url="https://tools.ietf.org/html/rfc2616#section-3.6">RFC 2616,
39 "3.6 Transfer Codings"</link>). 39 "3.6 Transfer Codings"</link>).
40 The "chunked" transfer-codings must not be used with HTTP/1.0. 40 The "chunked" transfer-codings must not be used with HTTP/1.0.
41 You’d need to either fix your backend application or upgrade 41 You’d need to either fix your backend application or upgrade
42 to nginx version 1.1.4 and newer, where an additional code 42 to nginx version 1.1.4 and newer, where an additional code
43 was introduced to handle such erratic backend behavior. 43 was introduced to handle such erratic backend behavior.