<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Content encoding error</title>
	<atom:link href="http://blog.1911census.co.uk/2009/01/content-encoding-error/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.1911census.co.uk/2009/01/content-encoding-error/</link>
	<description>official blog for 1911census.co.uk</description>
	<pubDate>Thu, 29 Jul 2010 14:39:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Secure Proxy</title>
		<link>http://blog.1911census.co.uk/2009/01/content-encoding-error/#comment-4772</link>
		<dc:creator>Secure Proxy</dc:creator>
		<pubDate>Wed, 21 Jul 2010 16:18:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.1911census.co.uk/?p=279#comment-4772</guid>
		<description>Anonymous proxy is the sefest proxy around in the world.It has huge features to protect your privacy. You can increase browsing speed through disable java scripts.</description>
		<content:encoded><![CDATA[<p>Anonymous proxy is the sefest proxy around in the world.It has huge features to protect your privacy. You can increase browsing speed through disable java scripts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shelley Durocher</title>
		<link>http://blog.1911census.co.uk/2009/01/content-encoding-error/#comment-4770</link>
		<dc:creator>Shelley Durocher</dc:creator>
		<pubDate>Wed, 21 Jul 2010 14:10:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.1911census.co.uk/?p=279#comment-4770</guid>
		<description>faster browsing speed through disable java scripts.</description>
		<content:encoded><![CDATA[<p>faster browsing speed through disable java scripts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Jervis</title>
		<link>http://blog.1911census.co.uk/2009/01/content-encoding-error/#comment-4104</link>
		<dc:creator>Rob Jervis</dc:creator>
		<pubDate>Fri, 18 Dec 2009 16:42:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.1911census.co.uk/?p=279#comment-4104</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>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.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Annetts</title>
		<link>http://blog.1911census.co.uk/2009/01/content-encoding-error/#comment-4102</link>
		<dc:creator>Simon Annetts</dc:creator>
		<pubDate>Fri, 18 Dec 2009 14:11:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.1911census.co.uk/?p=279#comment-4102</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>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.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kay</title>
		<link>http://blog.1911census.co.uk/2009/01/content-encoding-error/#comment-4082</link>
		<dc:creator>kay</dc:creator>
		<pubDate>Sat, 21 Nov 2009 07:47:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.1911census.co.uk/?p=279#comment-4082</guid>
		<description>So what should a mere mortal do?</description>
		<content:encoded><![CDATA[<p>So what should a mere mortal do?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jim backus</title>
		<link>http://blog.1911census.co.uk/2009/01/content-encoding-error/#comment-3682</link>
		<dc:creator>jim backus</dc:creator>
		<pubDate>Tue, 22 Sep 2009 15:36:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.1911census.co.uk/?p=279#comment-3682</guid>
		<description>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</description>
		<content:encoded><![CDATA[<p>This message is a result of a poisoned cache.</p>
<p>How to solve it:</p>
<p>write in your browser:  about:config ,and set this to false:</p>
<p>network.http.use-cache</p>
<p>Then try loading said site again. It will load.</p>
<p>Set it back to true, and the website fails to load, prompting the message.</p>
<p>Please spread the word to solve this problem quickly</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nate</title>
		<link>http://blog.1911census.co.uk/2009/01/content-encoding-error/#comment-2988</link>
		<dc:creator>Nate</dc:creator>
		<pubDate>Mon, 25 May 2009 00:57:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.1911census.co.uk/?p=279#comment-2988</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>My website is plagued with the &#8220;Content Encoding&#8221; problem also. </p>
<p>This issue only presents itself to the FireFox browser, my guess is FireFox is no longer the standard for properly rendering web pages.</p>
<p>Try google chrome instead.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Proxy Guy</title>
		<link>http://blog.1911census.co.uk/2009/01/content-encoding-error/#comment-2924</link>
		<dc:creator>Proxy Guy</dc:creator>
		<pubDate>Sun, 10 May 2009 19:11:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.1911census.co.uk/?p=279#comment-2924</guid>
		<description>Can I quote you in my report for school?</description>
		<content:encoded><![CDATA[<p>Can I quote you in my report for school?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iantester</title>
		<link>http://blog.1911census.co.uk/2009/01/content-encoding-error/#comment-2838</link>
		<dc:creator>iantester</dc:creator>
		<pubDate>Mon, 27 Apr 2009 01:44:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.1911census.co.uk/?p=279#comment-2838</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>It seems that we now have a definitive answer from our Technical team. </p>
<p>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. </p>
<p>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.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted Burrett</title>
		<link>http://blog.1911census.co.uk/2009/01/content-encoding-error/#comment-2832</link>
		<dc:creator>Ted Burrett</dc:creator>
		<pubDate>Fri, 24 Apr 2009 02:57:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.1911census.co.uk/?p=279#comment-2832</guid>
		<description>I noticed that this is not the first time   you write about this topic. Why have you chosen it again?</description>
		<content:encoded><![CDATA[<p>I noticed that this is not the first time   you write about this topic. Why have you chosen it again?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
