On 24/05/16 13:21, Francis Daly wrote:
On Tue, May 24, 2016 at 11:10:31AM +0100, Andrew Hutchings wrote:
Hi there,
As if by magic:
http://nginx.org/en/docs/http/ngx_http_core_module.html#chunked_transfer_encoding
Will that work here?
That directive seems to be about nginx sending a respo
Francis Daly Wrote:
---
> On Tue, May 24, 2016 at 11:10:31AM +0100, Andrew Hutchings wrote:
>
> Hi there,
>
> > As if by magic:
> http://nginx.org/en/docs/http/ngx_http_core_module.html#chunked_transf
> er_encoding
>
> Will that work here?
>
>
On Tue, May 24, 2016 at 11:10:31AM +0100, Andrew Hutchings wrote:
Hi there,
> As if by magic:
> http://nginx.org/en/docs/http/ngx_http_core_module.html#chunked_transfer_encoding
Will that work here?
That directive seems to be about nginx sending a response to a client,
and choosing not to send
Hey Andrew,
Thanks for your reply. Actually we tried that already and still faced the
same issue. It can easily be reproduced; send any GET request with header
"transfer-encoding: chunked".
We tried the below already.
chunked_transfer_encoding off;
proxy_buffering off;
Posted at Nginx Forum:
As if by magic:
http://nginx.org/en/docs/http/ngx_http_core_module.html#chunked_transfer_encoding
Kind Regards
Andrew
On 23/05/16 21:21, bclod wrote:
We have a client sending a GET request who is also erroneously sending a
transfer-encoding : chunked Header.
This is causing nginx to wait for
We have a client sending a GET request who is also erroneously sending a
transfer-encoding : chunked Header.
This is causing nginx to wait for the client to send data before the client
finally times out. Is there anyway to tell nginx to ignore this header? We
have asked the client to get their a
