I've been using v 188.8.131.52-1 over tinyproxy v 1.8.1-3 under ubuntu for several years with little or no trouble. At, I believe, the ubuntu 9.10 update, some sites began returning the Content Encoding Error. I don't really know when, I didn't hear about it until my 10-year-old mentioned not being able to get into the Amazon start-page (inner pages work fine). There are postings on this dating back to 2008. I've read about people running over tinyproxy and switching to squid and curing the problem, people with squid having the problem, and people curing the problem with miscellaneous small changes to config files. There are rather active discussions on launchpad concerning the problem in ubuntu (https://bugs.launchpad.net/ubuntu/+source/dansguardian/+bug/474475), and in debian (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536778), but it doesn't seem to be an issue here. Is this only a debain/ubuntu problem? Is there any movement here? Can I help?
Log in to post a comment.