Decompressing a compressed response from upstream, applying transformations and then compressing for downstream again

[Makailol Charls]

Hello Maxim,

Would you suggest the code change to achieve this?

Thanks,
Makailol


On Mon, Jan 20, 2014 at 7:18 PM, Maxim Dounin <mdounin at mdounin.ru> wrote:

> Hello!
>
> On Mon, Jan 20, 2014 at 09:40:30PM +0800, Rv Rv wrote:
>
> > Hello
> > Is there a way we can achieve the following when nginx is acting
> > as a reverse proxy
> >       1. Client sends HTTP request with Accept-Encoding as gzip
> >       2. Nginx proxy forwards the request with the request
> >       header intact
> >       3. Origin server sends a compressed response
> >       4. At the nginx proxy, we *decompress* the response, apply
> >       transformations on the response body and then *again*
> >       compress it
> > In other words, is there a way to use the functionality of gzip
> > and gunzip modules simultaneously for a processing a response
> > and in a particular order
>
> As of now, it's not possible without code modifications - mostly
> because there is no way to tell gunzip filter you want it to
> always decompress a response.  It can be achieved with minor code
> changes though.
>
> --
> Maxim Dounin
> http://nginx.org/
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140120/5226d152/attachment.html>