<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		xmlns:icbm="http://www.postneo.com/icbm/"
		>
<channel>
	<title>Comments on: Readers using IE</title>
	<atom:link href="http://technosailor.com/2006/05/26/readers-using-ie/feed/" rel="self" type="application/rss+xml" />
	<link>http://technosailor.com/2006/05/26/readers-using-ie/</link>
	<description>Web Technology and Real Life Merge</description>
	<lastBuildDate>Thu, 18 Mar 2010 02:16:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0-alpha</generator>
	<item>
		<title>By: Andy Merrett</title>
		<link>http://technosailor.com/2006/05/26/readers-using-ie/comment-page-1/#comment-236825</link>
		<dc:creator>Andy Merrett</dc:creator>
		<pubDate>Sun, 28 May 2006 21:21:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.technosailor.com/readers-using-ie/#comment-236825</guid>
		<description>I had a number of 412s but it was an issue with the web server, attempting to block spam  but being overzealous. It sounds like you have (had) a different problem though I&#039;ve not come across the server giving out 412 errors for this thing.&lt;br&gt;&lt;br&gt;Anyway, just in case anyone surfs here searching for 412 Precondition Failed error solutions, when it&#039;s to do with &#039;naughty&#039; words in either the referring or the target URL, etc. I solved it (on Textdrive servers) by putting the following directive in my .htaccess file:&lt;br&gt;&lt;br&gt;SecFilterEngine Off&lt;br&gt;&lt;br&gt;It means that spam attacks are potentially more likely but it does stop whatever rules a host has built in at server level.&lt;br&gt;&lt;br&gt;Not sure if this comment was helpful at all but there you go...</description>
		<content:encoded><![CDATA[<p>I had a number of 412s but it was an issue with the web server, attempting to block spam  but being overzealous. It sounds like you have (had) a different problem though I&#8217;ve not come across the server giving out 412 errors for this thing.</p>
<p>Anyway, just in case anyone surfs here searching for 412 Precondition Failed error solutions, when it&#8217;s to do with &#8216;naughty&#8217; words in either the referring or the target URL, etc. I solved it (on Textdrive servers) by putting the following directive in my .htaccess file:</p>
<p>SecFilterEngine Off</p>
<p>It means that spam attacks are potentially more likely but it does stop whatever rules a host has built in at server level.</p>
<p>Not sure if this comment was helpful at all but there you go&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Merrett</title>
		<link>http://technosailor.com/2006/05/26/readers-using-ie/comment-page-1/#comment-243647</link>
		<dc:creator>Andy Merrett</dc:creator>
		<pubDate>Sun, 28 May 2006 21:21:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.technosailor.com/readers-using-ie/#comment-243647</guid>
		<description>I had a number of 412s but it was an issue with the web server, attempting to block spam  but being overzealous. It sounds like you have (had) a different problem though I&#039;ve not come across the server giving out 412 errors for this thing.&lt;br&gt;&lt;br&gt;Anyway, just in case anyone surfs here searching for 412 Precondition Failed error solutions, when it&#039;s to do with &#039;naughty&#039; words in either the referring or the target URL, etc. I solved it (on Textdrive servers) by putting the following directive in my .htaccess file:&lt;br&gt;&lt;br&gt;SecFilterEngine Off&lt;br&gt;&lt;br&gt;It means that spam attacks are potentially more likely but it does stop whatever rules a host has built in at server level.&lt;br&gt;&lt;br&gt;Not sure if this comment was helpful at all but there you go...</description>
		<content:encoded><![CDATA[<p>I had a number of 412s but it was an issue with the web server, attempting to block spam  but being overzealous. It sounds like you have (had) a different problem though I&#8217;ve not come across the server giving out 412 errors for this thing.</p>
<p>Anyway, just in case anyone surfs here searching for 412 Precondition Failed error solutions, when it&#8217;s to do with &#8216;naughty&#8217; words in either the referring or the target URL, etc. I solved it (on Textdrive servers) by putting the following directive in my .htaccess file:</p>
<p>SecFilterEngine Off</p>
<p>It means that spam attacks are potentially more likely but it does stop whatever rules a host has built in at server level.</p>
<p>Not sure if this comment was helpful at all but there you go&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Merrett</title>
		<link>http://technosailor.com/2006/05/26/readers-using-ie/comment-page-1/#comment-6054</link>
		<dc:creator>Andy Merrett</dc:creator>
		<pubDate>Sun, 28 May 2006 20:21:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.technosailor.com/readers-using-ie/#comment-6054</guid>
		<description>I had a number of 412s but it was an issue with the web server, attempting to block spam  but being overzealous. It sounds like you have (had) a different problem though I&#039;ve not come across the server giving out 412 errors for this thing.

Anyway, just in case anyone surfs here searching for 412 Precondition Failed error solutions, when it&#039;s to do with &#039;naughty&#039; words in either the referring or the target URL, etc. I solved it (on Textdrive servers) by putting the following directive in my .htaccess file:

SecFilterEngine Off

It means that spam attacks are potentially more likely but it does stop whatever rules a host has built in at server level.

Not sure if this comment was helpful at all but there you go...</description>
		<content:encoded><![CDATA[<p>I had a number of 412s but it was an issue with the web server, attempting to block spam  but being overzealous. It sounds like you have (had) a different problem though I&#8217;ve not come across the server giving out 412 errors for this thing.</p>
<p>Anyway, just in case anyone surfs here searching for 412 Precondition Failed error solutions, when it&#8217;s to do with &#8216;naughty&#8217; words in either the referring or the target URL, etc. I solved it (on Textdrive servers) by putting the following directive in my .htaccess file:</p>
<p>SecFilterEngine Off</p>
<p>It means that spam attacks are potentially more likely but it does stop whatever rules a host has built in at server level.</p>
<p>Not sure if this comment was helpful at all but there you go&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
