Welcome! Log In Create A New Profile

Advanced

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

Jonathan Matthews
January 20, 2014 09:52AM
On 20 January 2014 14:34, Makailol Charls <makailol7@gmail.com> wrote:
> Hello Maxim,
>
> Would you suggest the code change to achieve this?

Instead of forking your own incompatible nginx version, I'd be tempted
to test this out:

Turn gzip on.
Always remove the Accept-Encoding header from the proxied request.
Perform the transformations on the uncompressed response.
Let nginx gzip the content on the way back to the client.

The ordering of the different modules you're using may spoil this
idea, of course, but I'd give it a go myself.

Cheers,
Jonathan

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

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

Rv Rv January 20, 2014 08:42AM

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

Maxim Dounin January 20, 2014 08:50AM

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

Makailol Charls January 20, 2014 09:36AM

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

Jonathan Matthews January 20, 2014 09:52AM

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

B.R. January 20, 2014 12:44PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 194
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready