Mercurial > hg > nginx-site

comparison xml/en/docs/faq/chunked_encoding_from_backend.xml @ 625:af3f38e349eb

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Removed terminal whitespace and fixed apostrophes used.
author Ruslan Ermilov <ru@nginx.com>
date Sat, 11 Aug 2012 04:55:25 +0000
parents 764fbac1b8b4
children 66a30a380fba
comparison
equal deleted inserted replaced
624:4b5163be537f 625:af3f38e349eb
2 Copyright (C) Nginx, Inc. 2 Copyright (C) Nginx, Inc.
3 --> 3 -->
4 4
5 <!DOCTYPE article SYSTEM "../../../../dtd/article.dtd"> 5 <!DOCTYPE article SYSTEM "../../../../dtd/article.dtd">
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="1">
12 12
13 <section> 13 <section>
14 14
15 <para> 15 <para>
16 <initial>Q:</initial> 16 <initial>Q:</initial>
17 My backend server appears to send HTTP/1.0 responses using 17 My backend server appears to send HTTP/1.0 responses using
18 chunked encoding but nginx doesn't handle it correctly. 18 chunked encoding but nginx doesn’t handle it correctly.
19 For instance, I'm using nginx as a frontend to my node.js 19 For instance, I’m using nginx as a frontend to my node.js
20 application and instead of pure JSON from backend, nginx 20 application and instead of pure JSON from backend, nginx
21 returns something framed in decimal numbers like 21 returns something framed in decimal numbers like
22 22
23 <programlisting> 23 <programlisting>
24 47 24 47
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="http://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.
44 </para> 44 </para>
45 45
46 </section> 46 </section>