Mercurial > hg > nginx-site
view xml/en/docs/faq/chunked_encoding_from_backend.xml @ 2060:237b67ef69a6
Improved win32 build instructions.
Added "--with-openssl-opt=no-asm" argument which is required since
OpenSSL 1.0.2, as OpenSSL started to use assembler by default in 1.0.0 and
then broke builds with MASM in OpenSSL 1.0.2 (ticket #1396).
While here, added "--with-debug", added missing "--http-scgi-temp-path" and
"--http-uwsgi-temp-path", updated OpenSSL to 1.0.2l, switched to slightly
more readable one-argument-per-line style in configure example, added
indentation to continuation lines, removed useless "--builddir=objs" argument
("objs" is the default), and removed useless "-f objs/Makefile" argument
in nmake (nginx generates appropriate Makefile in the current directory).
author | Maxim Dounin <mdounin@mdounin.ru> |
---|---|
date | Tue, 17 Oct 2017 17:57:36 +0300 |
parents | 66a30a380fba |
children | 4add6ae1296f |
line wrap: on
line source
<!-- Copyright (C) Nginx, Inc. --> <!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" rev="2"> <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> </para> <para> <initial>A:</initial> Your backend violates HTTP specification (see <link url="https://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 to nginx version 1.1.4 and newer, where an additional code was introduced to handle such erratic backend behavior. </para> </section> </article>