Mercurial > hg > nginx-site
diff xml/en/docs/faq/chunked_encoding_from_backend.xml @ 625:af3f38e349eb
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 |
line wrap: on
line diff
--- a/xml/en/docs/faq/chunked_encoding_from_backend.xml +++ b/xml/en/docs/faq/chunked_encoding_from_backend.xml @@ -4,7 +4,7 @@ <!DOCTYPE article SYSTEM "../../../../dtd/article.dtd"> -<article name="Why nginx doesn't handle chunked encoding +<article name="Why nginx doesn’t handle chunked encoding responses from my backend properly?" link="/en/docs/faq/chunked_encoding_from_backend.html" lang="en" @@ -15,8 +15,8 @@ <para> <initial>Q:</initial> My backend server appears to send HTTP/1.0 responses using -chunked encoding but nginx doesn't handle it correctly. -For instance, I'm using nginx as a frontend to my node.js +chunked encoding but nginx doesn’t handle it correctly. +For instance, I’m using nginx as a frontend to my node.js application and instead of pure JSON from backend, nginx returns something framed in decimal numbers like @@ -38,7 +38,7 @@ Your backend violates HTTP specification <link url="http://tools.ietf.org/html/rfc2616#section-3.6">RFC 2616, "3.6 Transfer Codings"</link>). The "chunked" transfer-codings must not be used with HTTP/1.0. -You'd need to either fix your backend application or upgrade +You’d need to either fix your backend application or upgrade to nginx version 1.1.4 and newer, where an additional code was introduced to handle such erratic backend behavior. </para>