Welcome! Log In Create A New Profile

Advanced

Re: content-type header charset info problem

May 11, 2012 10:10AM
Yes, I'd expect the charset definition in content type header even if the content is gzipped.

Reading the RFC2616, there is no mutually excludent rule that prohibits the charset to be declared after gzip encoding.

Unfortunately, I'm using nginx 1.0.14 and cannot apply patches to it without having it gone through extensive testing and benchmarks again, we're changing a very important section of our infrastructure and changes like these are always a hard work.

I haven't had the time to check if this patch is applied to the trunk, or the latest stable version of nginx. If the charset module is already with that patch on 1.2 branch then it will be much easier to start the 1.2.X branch testing and benchmarking by our capacity planning and testing team to homologate that version for our infrastructure.

Thank you.
Subject Author Posted

content-type header charset info problem

djeps May 10, 2012 11:51AM

Re: content-type header charset info problem

Maxim Dounin May 10, 2012 02:36PM

Re: content-type header charset info problem

djeps May 10, 2012 04:36PM

Re: content-type header charset info problem

Maxim Dounin May 11, 2012 03:12AM

Re: content-type header charset info problem

djeps May 11, 2012 10:10AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 63
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready