GET request with transfer-encoding causing issue

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 act together; but in the mean time
was
wondering if there was anything we could do.

Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,267076,267076#msg-267076

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:


nginx mailing list
[email protected]
http://mailman.nginx.org/mailman/listinfo/nginx


Andrew H. (LinuxJedi)
Technical Product Manager, NGINX Inc.

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:
https://forum.nginx.org/read.php?2,267076,267084#msg-267084

Francis D. Wrote:

That directive seems to be about nginx sending a response to a client,
nginx mailing list
[email protected]
http://mailman.nginx.org/mailman/listinfo/nginx

See my other reply; it does not work (we had already tried it before
asking).

Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,267076,267086#msg-267086

On Tue, May 24, 2016 at 11:10:31AM +0100, Andrew H. 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 it “chunked” even though it normally would.

This problem seems to be nginx reading a request from a client, where
the request is malformed.

f

Francis D. [email protected]

On 24/05/16 13:21, Francis D. wrote:

This problem seems to be nginx reading a request from a client, where
the request is malformed.

Ah, good point. No, it won’t help in this case. I’m not sure anything
will without hacking code onto NGINX. It does require clients to
somewhat meet HTTP protocol specifications unfortunately.

Kind Regards

Andrew H. (LinuxJedi)
Technical Product Manager, NGINX Inc.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs