Bug#524341: Further info on Polipo Accept-Encoding problem

2014-11-02 Thread Rolf Leggewie
On Wed, 27 Jul 2011 17:40:19 +0200 Juliusz Chroboczek j...@pps.jussieu.fr wrote: WHich version of Polipo? should Apache be sending back a different ETag or something to indicate that the content that may be returned must be uncompressed? Yes, it should. That's a well-known bug in some

Bug#524341: Further info on Polipo Accept-Encoding problem

2014-11-02 Thread Trent W. Buck
Rolf Leggewie wrote: J.P. and Trent, do you still experience this problem? I stopped using polipo a couple of years ago, because the benefits weren't worth the grief it gave me (from crashing, and from not working with some sites). -- To UNSUBSCRIBE, email to

Bug#524341: Further info on Polipo Accept-Encoding problem

2011-07-27 Thread Juliusz Chroboczek
WHich version of Polipo? should Apache be sending back a different ETag or something to indicate that the content that may be returned must be uncompressed? Yes, it should. That's a well-known bug in some versions of Apache's mod_gzip. This is supposed to be worked around by the default

Bug#524341: Further info on Polipo Accept-Encoding problem

2011-07-25 Thread J.P. Larocque
Hi, I ran into this same issue today (Debian BTS #524341). I'm running: Polipo, Debian polipo 1.0.4.1-1.1 Apache, Debian apache2-mpm-prefork 2.2.16-6+squeeze1 Chromium, Ubuntu chromium-browser 12.0.742.112~r90304-0ubuntu0.11.04.1, and MSIE 6.0.2900.5512.xpsp_sp3_gdr.101209-1647 When