# GET request with transfer-encoding causing issue

**URL:** <https://www.ruby-forum.com/t/get-request-with-transfer-encoding-causing-issue/244665>\
**Category:** NGINX\
**Created:** [May 23, 2016, 10:21pm UTC](https://www.ruby-forum.com/t/get-request-with-transfer-encoding-causing-issue/244665 "2016-05-23T22:21:42Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rafa\_F](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/958977/32.png) [@Rafa\_F](https://www.ruby-forum.com/u/Rafa_F)\
**Post date:** [May 23, 2016, 10:21pm UTC](https://www.ruby-forum.com/t/get-request-with-transfer-encoding-causing-issue/244665/1 "2016-05-23T22:21:42Z")

</div>

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:

> **[GET request with transfer-encoding causing issue](https://forum.nginx.org/read.php?2,267076,267076#msg-267076)**
>
> 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...

---

<div class="post-metadata">

**Author:** ![bclod](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/f19dbf/32.png) [@bclod](https://www.ruby-forum.com/u/bclod)\
**Post date:** [May 24, 2016, 12:11pm UTC](https://www.ruby-forum.com/t/get-request-with-transfer-encoding-causing-issue/244665/2 "2016-05-24T12:11:12Z")

</div>

As if by magic:

> **[Module ngx\_http\_core\_module](http://nginx.org/en/docs/http/ngx_http_core_module.html#chunked_transfer_encoding)**
>
> This directive appeared in version 1.11.8.

Kind Regards  
Andrew

On 23/05/16 21:21, bclod wrote:

> * * *
> 
> nginx mailing list  
> [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
> [mailman.nginx.org archive](http://mailman.nginx.org/mailman/listinfo/nginx)

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

---

<div class="post-metadata">

**Author:** ![bclod](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/f19dbf/32.png) [@bclod](https://www.ruby-forum.com/u/bclod)\
**Post date:** [May 24, 2016, 2:17pm UTC](https://www.ruby-forum.com/t/get-request-with-transfer-encoding-causing-issue/244665/3 "2016-05-24T14:17:58Z")

</div>

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:

> **[Re: GET request with transfer-encoding causing issue](https://forum.nginx.org/read.php?2,267076,267084#msg-267084)**
>
> 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...

---

<div class="post-metadata">

**Author:** ![bclod](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/f19dbf/32.png) [@bclod](https://www.ruby-forum.com/u/bclod)\
**Post date:** [May 24, 2016, 2:24pm UTC](https://www.ruby-forum.com/t/get-request-with-transfer-encoding-causing-issue/244665/4 "2016-05-24T14:24:24Z")

</div>

## Francis D. Wrote:

> That directive seems to be about nginx sending a response to a client,  
> nginx mailing list  
> [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
> [mailman.nginx.org archive](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](https://forum.nginx.org/read.php?2,267076,267086#msg-267086)

---

<div class="post-metadata">

**Author:** ![bclod](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/f19dbf/32.png) [@bclod](https://www.ruby-forum.com/u/bclod)\
**Post date:** [May 24, 2016, 2:21pm UTC](https://www.ruby-forum.com/t/get-request-with-transfer-encoding-causing-issue/244665/5 "2016-05-24T14:21:28Z")

</div>

On Tue, May 24, 2016 at 11:10:31AM +0100, Andrew H. wrote:

Hi there,

> As if by magic:  
> [Module ngx\_http\_core\_module](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. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)

---

<div class="post-metadata">

**Author:** ![bclod](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/f19dbf/32.png) [@bclod](https://www.ruby-forum.com/u/bclod)\
**Post date:** [May 24, 2016, 2:30pm UTC](https://www.ruby-forum.com/t/get-request-with-transfer-encoding-causing-issue/244665/6 "2016-05-24T14:30:49Z")

</div>

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.