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…
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…
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…
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?
On Tue, Nov 23, 2010 at 5:44 AM, John Axel E. [email protected]
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.