- March 15, 2007 at 4:44 pm #13940
Why do I keep getting this error when I try to access a page?
- February 11, 2011 at 1:33 pm #13954
The SECFilter command is useful in disabling the 406 error, but be careful with what you let through. As the article mentions, I would target specific file patterns and URL’s. Letting everything through is too much of a security risk (that’s why SECFilter was implemented by Apache in the first place).
- April 9, 2008 at 4:05 am #13953
I wanna use this “SecFilterEngine on” but still cannot load the pages correctly.. is there any code to solve this problems? I mean use “SecFilterEngine On” but can load any webpages correctly?
- May 5, 2009 at 9:15 pm #13952
If your Host Server is throwing back this error then a simple page refresh – using the html code below on your 406 error page will correct the issue:
- July 18, 2011 at 8:37 am #13951
What an annoying error! Not an acceptable representation of this resource…WTF? Why oh why can’t engineers put things into English the first time. It shouldn’t be up to the thousands of web designers/ developers out there to restate error message in hundreds of different ways if a little upfront effort by the initial engineers could make things easier for all of us! Right?
- November 23, 2010 at 10:29 am #13946
So a 406 error is specific to Apache servers? Can’t one get the error otherwise?
- July 15, 2009 at 4:43 am #13943
Hello, yesterday it was ok… but from today it shows this 406 error. Please help me solve this problem.
- March 17, 2007 at 8:06 pm #13942
406 Error (Not Acceptable)
This is due to Apache mod_security that is turned on by default. While you can use the following to diagnose the problem (turning the filter off should resolve the issue):
It’s important to leave the filter on as it helps prevent spam and injection attacks. What you need to do is figure out (ask your hosting provider if you need help) the phrases that are triggering the filter. Typically these will include phrases that include possible commands such as “ftp,” “telnet,” “ssh,” etc. Once you know which ones are, you can modify the filter to permit the page that is not loading (scan your logs or Google sitemap for 406 errors to find all the pages experiencing this problem):
SecFilterSelective "POST_PAYLOAD" "allow these words" "allow,nolog"
You must be logged in to reply to this topic.