On 05-feb-09, at 17:37, Stefan de Konink wrote: > On Thu, 5 Feb 2009, Alvaro Lopez Ortega wrote: > >> Sorry? That doesn't make any sense. > > Just forget the content-encoding or content-type part and observe the > result ;) The wiki thingie that is on the proud list also made that > error, > but then again that was a php site that was doing compression > itself, but > not setting the proper headers.
So, the thing is.. if the back-end server gzip-encodes the reply, it *must* also include the "Content-Encoding: gzip" header, otherwise it would be sending a broken response (causing trouble to the proxies along the way, and most probably to some browsers). As long as the back-end server response is HTTP compliant, there shouldn't be any problem. -- Octality http://www.octality.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
