From: Jenny L. <bod...@li...> - 2012-05-22 14:16:43
|
> > The point is... i am losing gzip functionality on the client. > > > > I have: enable-compression 1, compression-level 1 > > > > If i remove the filter above, gzip functionality works. > > > > In the full log, I have: > > > > 2012-05-21 07:16:13.375 20041c58 Header: Crunching: Content-Encoding: gzip > > 2012-05-21 07:16:13.375 20041c58 Header: Content modified with no Content-Length header set. Created: Content-Length: 189142. > > > > it is just that, privoxy is somehow removing this header to the client. So client is not able to do compression. > > Privoxy has to decompress the content to filter it, > at which point the header has to be removed as well. > > With "enable-compression 1" and if the client supports deflate > compression, Privoxy will compress the filtered content and add > a new header. > > In the log this looks like this: > > 14:36:00.916 009 Header: scan: Accept-Encoding: gzip, deflate > [...] > 14:36:01.721 009 Re-Filter: Compressed content from 10021 to 3688 bytes. Compression level: 5 > 14:36:01.722 009 Header: Adjusted Content-Length to 3688 > 14:36:01.722 009 Header: Added header: Content-Encoding: deflate > > While Privoxy can decompress gzip-encoded content, > it can currently only compress with deflate. > > If the client doesn't signal deflate support, > Privoxy will not recompress the content. > Fabian thank you for the information. However, I am using curl with --compressed option and it is sending: deflate, gzip Still no success. Also, why not support gzip instead of deflate? As far as I know, most servers/clients send gzip. Jenny |