Mercurial > hg > nginx-site
comparison xml/en/docs/faq/chunked_encoding_from_backend.xml @ 196:aafe530e7d6f
- Added faq/ and more q&a as previously agreed
author | Andrey Alexeev <andrew@nginx.com> |
---|---|
date | Wed, 23 Nov 2011 15:32:04 +0000 |
parents | |
children | ec4626d04879 |
comparison
equal
deleted
inserted
replaced
195:e83a59eee5cf | 196:aafe530e7d6f |
---|---|
1 <!DOCTYPE article SYSTEM "../../../../dtd/article.dtd"> | |
2 | |
3 <article name="Why nginx doesn't handle chunked encoding | |
4 responses from my backend properly?" | |
5 link="/en/docs/faq/chunked_encoding_from_backend.html" | |
6 lang="en"> | |
7 | |
8 <section> | |
9 | |
10 <para> | |
11 <initial>Q:</initial> | |
12 My backend server appears to send HTTP/1.0 responses using | |
13 chunked encoding but nginx doesn't handle it correctly. | |
14 For instance, I'm using nginx as a frontend to my node.js | |
15 application and instead of pure JSON from backend nginx | |
16 returns something framed in decimal numbers like | |
17 | |
18 <programlisting> | |
19 47 | |
20 {"error":"query error","message":"Parameter(s) missing: user,password"} | |
21 0 | |
22 </programlisting> | |
23 | |
24 </para> | |
25 | |
26 <para> | |
27 | |
28 </para> | |
29 | |
30 <para> | |
31 <initial>A:</initial> | |
32 Your backend violates HTTP/1.0 specification (see | |
33 <a href="http://tools.ietf.org/html/rfc2616#section-3.6">RFC 2616, | |
34 "3.6 Transfer Codings"</a> | |
35 The "chunked" transfer-codings must not be used with HTTP/1.0. | |
36 You'd need to either fix your backend application or upgrade | |
37 to nginx version 1.1.4 and newer, where an additional code | |
38 was introduced to handle such erratic backend behavior. | |
39 </para> | |
40 | |
41 </section> | |
42 | |
43 </article> |