--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/xml/en/docs/faq/chunked_encoding_from_backend.xml	Wed Nov 23 15:32:04 2011 +0000
@@ -0,0 +1,43 @@
+<!DOCTYPE article SYSTEM "../../../../dtd/article.dtd">
+
+<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">
+
+<section>
+
+<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
+application and instead of pure JSON from backend nginx
+returns something framed in decimal numbers like
+
+<programlisting>
+47
+{"error":"query error","message":"Parameter(s) missing: user,password"}
+0
+</programlisting>
+
+</para>
+
+<para>
+&nbsp;
+</para>
+
+<para>
+<initial>A:</initial>
+Your backend violates HTTP/1.0 specification (see
+<a href="http://tools.ietf.org/html/rfc2616#section-3.6">RFC 2616,
+"3.6 Transfer Codings"</a>
+The "chunked" transfer-codings must not be used with HTTP/1.0.
+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>
+
+</section>
+
+</article>