Comments on: Content encoding error

By: Mens Hair Growth Resource hair loss vitamins

Mens Hair Growth Resource hair loss vitamins — Wed, 01 Feb 2012 13:57:57 +0000

Mens Hair Growth Resource hair loss vitamins…

[...]1911census.co.uk blog » Blog Archive » Content encoding error[...]…

By: heating repair in middleton

heating repair in middleton — Thu, 05 Jan 2012 07:31:14 +0000

Wow that was strange. I just wrote an extremely long comment but after I clicked submit my comment didn’t show up. Grrrr… well I’m not writing all that over again. Regardless, just wanted to say wonderful blog!

By: David

David — Fri, 18 Feb 2011 22:58:18 +0000

The solution left by Jim Backus leaves me with the same result as the solution at the top, which is that when I try to access Yahoo! Mail (which I am the most concerned about) the page simply comes up as a blank

By: Rob Jervis

Rob Jervis — Fri, 18 Dec 2009 16:42:04 +0000

We provide internet access for 250 schools and 30 public libraries, non of which are currently able to access the site due to this issue with Squid. Please could someone take a look at this as a matter of urgency. Please feel free to contact me if you need anyone to test the service once reconfiguration has taken place. This is the only site our users are having issues with.

By: Simon Annetts

Simon Annetts — Fri, 18 Dec 2009 14:11:04 +0000

I think the configuration of this site is broken. Period. No other sites exhibit this problem whether they are using IIS6, compression or are being accessed via a squid proxy. I urge the webadmins of this site to review their web server configuration and to test with a browser running through a squid web cache. As an earlier poster pointed out, many if not all univeristies and libraries are likely to be pushing their users through a squid proxy server. Asking users to change their browser settings is just buck passing.

By: kay

kay — Sat, 21 Nov 2009 07:47:59 +0000

So what should a mere mortal do?

By: jim backus

jim backus — Tue, 22 Sep 2009 15:36:03 +0000

This message is a result of a poisoned cache.

How to solve it:

write in your browser: about:config ,and set this to false:

network.http.use-cache

Then try loading said site again. It will load.

Set it back to true, and the website fails to load, prompting the message.

Please spread the word to solve this problem quickly

By: Nate

Nate — Mon, 25 May 2009 00:57:10 +0000

My website is plagued with the “Content Encoding” problem also.

This issue only presents itself to the FireFox browser, my guess is FireFox is no longer the standard for properly rendering web pages.

Try google chrome instead.

By: Proxy Guy

Proxy Guy — Sun, 10 May 2009 19:11:54 +0000

Can I quote you in my report for school?

By: iantester

iantester — Mon, 27 Apr 2009 01:44:53 +0000

It seems that we now have a definitive answer from our Technical team.

1911census.co.uk uses Microsoft IIS6 web servers, which when queried, always provide HTTP 1.1 encoded pages. Some proxy servers (e.g some versions of Squid) cannot process these as they only support HTTP 1.0. This means that if users are accessing the site via a network unable to process HTTP 1.1, they will get blank pages returned unless using a hack to bypass the proxy server.

Recommended fix: upgrade to a proxy server able to process HTTP 1.1 - unfortunately there is no option currently to make IIS6 return a 1.0 response (unfortunate but true). Squid 2.7 will support chunked headers.