Quote:
Originally Posted by buro9
I've got a new bug/weirdness going on:
http://www.bowlie.com/forum/tags/superlong/
That page returns a 403 not authorised.
Yet if you click Tags in the top menu, search for 'super'... you'll see that 'superlong' is returned in the results, but clicking on it triggers the 403.
Why would this be? Why would a tag return a 403?
The thread tagged with that is part of the auto-generated tags and relates to this:
http://www.bowlie.com/forum/music-ro...soul-mp3s.html
The record in the database include the tag 'superlong' and is for that threadid.
Can't think why the 403 gets generated.
|
This is NOT a bug.
It's because of the word 'perl' being in the underlying querystring. I have a lot of server defenses and this one I put in place ages ago to defend against the PHP vunerability that was bouncing around two winters ago.
Anyhow, amusing PM from and to phlogiston on the matter, who I have to thank for finding it and reminding me of it:
Quote:
Originally Posted by buro9
Quote:
Originally Posted by phlogiston
I had a muck around trying to narrow down the 403 and I'm pretty certain it's from "perl" in the tagname (sniperlong 403'd as did a couple others) - do you have a forum named that which vbseo is trying to redirect to or a server setup which could use it as a special directory name or something? :S (servers are beyond my knowledge)
btw - I totally apologise if I may have killed your server by attempting going to http://www.bowlie.com/forum/tags/perl/
I was trying out a few tags and everything was fine until then. Afterwards server death
Ermm, sorry. Obv didn't want to post this in the public thread and having everyone else try incase it is the problem...
Ryan.
|
Heh, you must've been the one that just triggered my server defenses then:
Quote:
[Mon Nov 20 16:58:00 2006] [error] [client xx.xxx.xxx.xx] mod_security: Access denied with code 403. Pattern match "perl" at QUERY_STRING. [hostname "www.bowlie.com"] [uri "/forum/tags/index.php?tag =superlong"]
[Mon Nov 20 16:59:28 2006] [error] [client xx.xxx.xxx.xx] mod_security: Access denied with code 403. Pattern match "perl" at QUERY_STRING. [hostname "www.bowlie.com"] [uri "/forum/tags/index.php?tag=soperlongr"]
[Mon Nov 20 16:59:35 2006] [error] [client xx.xxx.xxx.xx] mod_security: Access denied with code 403. Pattern match "perl" at QUERY_STRING. [hostname "www.bowlie.com"] [uri "/forum/tags/index.php?tag=soperlong"]
[Mon Nov 20 17:00:15 2006] [error] [client xx.xxx.xxx.xx] mod_security: Access denied with code 403. Pattern match "perl" at QUERY_STRING. [hostname "www.bowlie.com"] [uri "/forum/tags/index.php?tag=sniperlong"]
[Mon Nov 20 17:00:43 2006] [error] [client xx.xxx.xxx.xx] mod_security: Access denied with code 403. Pattern match "perl" at QUERY_STRING. [hostname "www.bowlie.com"] [uri "/forum/tags/index.php?tag=perlong"]
|
That was indeed the solution, and thanks so much for hitting it several times
I'll update the post to stop any panic
Oh, and the server is fine... it just added you to the iptables and blocked you. In 15 minutes the block will be lifted. It's a set of defenses to stop any DoS or bot attack. I'd just totally forgotten about it
Thanks again 
|
So, that was NOT a bug, it's my server security doing it's job
And if anyone is curious, it's mod_security in addition to iptables that does that