http://blog.spind.net/2009/05/13/the-mysterious-case-of-the-501-error/ Stories from the trenches of System Administration Tue, 15 Nov 2011 09:34:33 +0000 hourly 1 http://wordpress.org/?v=3.3 http://blog.spind.net/2009/05/13/the-mysterious-case-of-the-501-error/comment-page-1/#comment-18586 Shea Sat, 13 Aug 2011 00:15:41 +0000 http://blog.spind.net/?p=137#comment-18586 Thank you so much for this post. Taking the time to investigate pays off. Much rather rid the problem then rid a whole feature. Thank you so much for this post. Taking the time to investigate pays off. Much rather rid the problem then rid a whole feature.

]]> http://blog.spind.net/2009/05/13/the-mysterious-case-of-the-501-error/comment-page-1/#comment-3149 pabiltostar Thu, 16 Jul 2009 14:15:50 +0000 http://blog.spind.net/?p=137#comment-3149 I appreciate your approach to understanding and fixing at the source. As you know mod_security will filter on other tokens and phrases as well, such as embedding sql queries in your post. My work-around, rather than crippling the security at each discovery, is maybe more simple-minded but just as effective; alter the spelling of the offending tokens. E.g., write /e t c or s elect instead. I discovered the issue on my first blog post ever, which was on sql. Took me hours to figure out (since I can't access web logs) before it clicked that it could look like sql injection. But I didn't actually know the root cause. Thanks for your post (and the one on techpulp you're responding to). I appreciate your approach to understanding and fixing at the source. As you know mod_security will filter on other tokens and phrases as well, such as embedding sql queries in your post. My work-around, rather than crippling the security at each discovery, is maybe more simple-minded but just as effective; alter the spelling of the offending tokens. E.g., write /e t c or s elect instead. I discovered the issue on my first blog post ever, which was on sql. Took me hours to figure out (since I can’t access web logs) before it clicked that it could look like sql injection. But I didn’t actually know the root cause. Thanks for your post (and the one on techpulp you’re responding to).

]]>