Unfortunately, I can't comment on cnst's post - so I'm going to answer here.
nginx_http_proxy module by default talks with the upstream in HTTP/1.0.
This can be changed with the directive
This might also be the cause for your script to return a HTTP/1.0 answer, although chunked coding and status code
307 don't exist in this version.
You shouldn't use chunked coding with a redirect either, as this doesn't really make sense.
Additionally, it seems like nginx doesn't pass chunks from the upstream to the client one by one, but it buffers the upstream's response.
Content-Length header field is ignored because it is against the definition.
I had to look at the source code of the module because all this appears to be undocumented.
You may want to try out the
nginx_tcp_proxy_module to proxy the chunked content as raw TCP data: Module at Github
module has support for
, of which one (
) controls whether the response should be buffered or not.
Adding this header (
X-Accel-Buffering: no) to the backend's response will cause nginx to directly pass chunks to the client.
This header allows to control buffering on an per-request basis.
The module also has a configuration directive
proxy_buffering to enable or disable response buffering (not buffering means sending chunks will work).
Proxy buffering (both header and directive based) is documented here.