# Nginx proxying chunked transfer encoding? **URL:** \ **Category:** NGINX\ **Created:** [November 22, 2010, 8:49pm UTC](https://www.ruby-forum.com/t/nginx-proxying-chunked-transfer-encoding/199489 "2010-11-22T20:49:02Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Dobai-Pataky\_BSSSSl](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/77aa72/32.png) [@Dobai-Pataky\_BSSSSl](https://www.ruby-forum.com/u/Dobai-Pataky_BSSSSl)\ **Post date:** [November 22, 2010, 8:49pm UTC](https://www.ruby-forum.com/t/nginx-proxying-chunked-transfer-encoding/199489/1 "2010-11-22T20:49:02Z")
I’ve been searching for a solution to an issue I have when I proxy requests that return with chunked transfer encoding. I’ve never gotten an answer, so I’ll make the question really simple: Can Nginx proxy “something” that returns with chunked transfer encoding on a GET? What I mean is, if what I’m proxying cannot be configured to return anything other than chunked encoding, can nginx proxy it properly? I’ve not gotten it to work anyway… Regards, John ---
**Author:** ![lgas](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/a87d85/32.png) [@lgas](https://www.ruby-forum.com/u/lgas)\ **Post date:** [November 22, 2010, 10:33pm UTC](https://www.ruby-forum.com/t/nginx-proxying-chunked-transfer-encoding/199489/2 "2010-11-22T22:33:59Z")
Hello! On Mon, Nov 22, 2010 at 08:47:39PM +0100, John Axel E. wrote: > Can Nginx proxy “something” that returns with chunked transfer encoding on a > GET? > What I mean is, if what I’m proxying cannot be configured to return anything > other than > chunked encoding, can nginx proxy it properly? I’ve not gotten it to work > anyway… No. Maxim D. ---
**Author:** ![lgas](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/a87d85/32.png) [@lgas](https://www.ruby-forum.com/u/lgas)\ **Post date:** [November 22, 2010, 10:45pm UTC](https://www.ruby-forum.com/t/nginx-proxying-chunked-transfer-encoding/199489/3 "2010-11-22T22:45:17Z")
Thanks so much for replying! I’m very very saddened though since I love nginx so much but now must part ways. Is there any sort of plan to support this in the future? I guess it might mean you must support http 1.1 to backends… 22 nov 2010 kl. 22.32 skrev Maxim D.: ---
**Author:** ![lgas](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/a87d85/32.png) [@lgas](https://www.ruby-forum.com/u/lgas)\ **Post date:** [November 22, 2010, 11:09pm UTC](https://www.ruby-forum.com/t/nginx-proxying-chunked-transfer-encoding/199489/4 "2010-11-22T23:09:09Z")
Thanks, I already did check that out but I got the impression that it only does chunked input, but perhaps I’m wrong? Would Nginx proxy chunked responses from backend using that module? 22 nov 2010 kl. 23.04 skrev Eugaia: ---
**Author:** ![lgas](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/a87d85/32.png) [@lgas](https://www.ruby-forum.com/u/lgas)\ **Post date:** [November 22, 2010, 11:05pm UTC](https://www.ruby-forum.com/t/nginx-proxying-chunked-transfer-encoding/199489/5 "2010-11-22T23:05:24Z")
Hi, Check out the chunkin module for Nginx : > **[GitHub - agentzh/chunkin-nginx-module: HTTP 1.1 chunked-encoding request body...](https://github.com/agentzh/chunkin-nginx-module)** > > HTTP 1.1 chunked-encoding request body support for Nginx - GitHub - agentzh/chunkin-nginx-module: HTTP 1.1 chunked-encoding request body support for Nginx This should probably suit your needs. Marcus. ---
**Author:** ![lgas](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/a87d85/32.png) [@lgas](https://www.ruby-forum.com/u/lgas)\ **Post date:** [November 23, 2010, 8:19am UTC](https://www.ruby-forum.com/t/nginx-proxying-chunked-transfer-encoding/199489/6 "2010-11-23T08:19:19Z")
On Tue, Nov 23, 2010 at 5:44 AM, John Axel E. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > Thanks so much for replying! I’m very very saddened though since I love nginx so > much but > now must part ways. We do really want this feature as well. We’re now using ngx\_proxy as a non-blocking HTTP client for our ngx\_lua applications (we also use ngx\_drizzle as the non-blocking mysql client and ngx\_memc for the memcached/tokyotyrant). > Is there any sort of plan to support this in the future? I guess it might mean > you must support http 1.1 to backends… Our team will try implementing ngx\_proxy\_more or something like that to include basic HTTP 1.1 (keepalive + chunked) support to ngx\_proxy in the first quarter of the next year if Igor does not do that himself already. Cheers, -agentzh ---
**Author:** ![lgas](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/a87d85/32.png) [@lgas](https://www.ruby-forum.com/u/lgas)\ **Post date:** [November 24, 2010, 5:41am UTC](https://www.ruby-forum.com/t/nginx-proxying-chunked-transfer-encoding/199489/7 "2010-11-24T05:41:06Z")
If you do implement a HTTP/1.1 backend support module me and alot of people will love you. ---
**Author:** ![lgas](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/a87d85/32.png) [@lgas](https://www.ruby-forum.com/u/lgas)\ **Post date:** [November 22, 2010, 11:59pm UTC](https://www.ruby-forum.com/t/nginx-proxying-chunked-transfer-encoding/199489/8 "2010-11-22T23:59:52Z")
Hi, I’ve not used the chunkin module personally. Having just had a quick look at the description, it appears that you are right that it’s only for inputs. Perhaps check out Apache Traffic Server / HAProxy? Not sure if either of them support chunked responses or not, but I expect that one of them does. Cheers, Marcus.