I feel very bad that my latest theme update last month has caused a lot of issues with readers - particularly readers that have had Internet Explorer forced on them by corporate entities who obviously have no sense of security. Many readers have been emailing me (there have been 5 emails in the past week) complaining about a “Precondition Failed” error. Sometimes it prevents readers from accessing the site. Other times it prevents readers from commenting. I am certain I know what is causing the problem, but I’m not sure how to fix it. I’ve emailed the theme designer for help.
The problem is caused, again, for corporate readers behind proxies. Not all proxies. It depends on the proxy configuration though. IE needs to identify itself to a proxy to get the proxy to allow traffic through. I believe the AJAX that is used in the live search and the commenting is not identifying itself properly and needs to be fixed.
In the meantime, grab a Bloglines account - they are free. Also, download Firefox or Opera or one of those other cool browsers that don’t misbehave like IE. Browse Happy with Firefox.
Update: I think I might have fixed this. By using the theme’s built in browser sniffer, I can determine if you’re using IE and if you are using IE, disable all the glitz and glamour of the nice commenting and the live search.
However, if you use a real browser, all the niceities remain. God, I hate IE.
Stumble it!
About the Author: Aaron Brazell is the lead editor of Technosailor.com and a social media expert. His passion is to see companies and individuals use the internet and web technologies wisely and effectively to promote their brands and companies. He is Business Development Manager for Lijit and he worked as Director of Technology at b5media from 2005-2008 and is currently an independent consultant.
Add New Comment
Viewing 1 Comment
Thanks. Your comment is awaiting approval by a moderator.
Do you already have an account? Log in and claim this comment.
Do you already have an account? Log in and claim this comment.
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:
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...
Add New Comment