<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Technosailor - Latest Comments in Readers using IE</title><link>http://technosailor.disqus.com/</link><description></description><atom:link href="https://technosailor.disqus.com/readers_using_ie/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Sun, 28 May 2006 16:21:54 -0000</lastBuildDate><item><title>Re: Readers using IE</title><link>http://technosailor.com/2006/05/26/readers-using-ie/#comment-1032234</link><description>&lt;p&gt;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've not come across the server giving out 412 errors for this thing.&lt;/p&gt;&lt;p&gt;Anyway, just in case anyone surfs here searching for 412 Precondition Failed error solutions, when it's to do with 'naughty' 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;/p&gt;&lt;p&gt;SecFilterEngine Off&lt;/p&gt;&lt;p&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;/p&gt;&lt;p&gt;Not sure if this comment was helpful at all but there you go...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andy Merrett</dc:creator><pubDate>Sun, 28 May 2006 16:21:54 -0000</pubDate></item></channel></rss>