Been seeing a lot of these over the past few days. Guess it shouldn't be too hard to see why the requests have been denied.
[edited by: Ocean10000 at 3:31 am (utc) on Dec 20, 2013] [edit reason] Broke autolink [/edit]
dstiles
4:59 pm on Dec 24, 2013 (gmt 0)
I've seen a lot of weird yahoo hits overnight in the 68.180.224.0/24 range. They carry the proper slurp UA below but use a proxy WITHIN the same /24 range. For example...
Proxying within the same range? There would appear to be some testing going on. rDNS does not admit it's a crawler so it got banned anyway but I have now 403'd the whole /24.
[edited by: phranque at 9:07 pm (utc) on Dec 24, 2013] [edit reason] fix url [/edit]
Are you saying that the UA string begins with the literal text "User-Agent: "? Or was that just an artifact of typing the post?
Do you really want to lock people out from robots.txt? It just gives them an excuse to say "Well, I wanted to obey robots.txt ::whine:: but they wouldn't let me see it!"
bobothecat2
11:36 am on Dec 25, 2013 (gmt 0)
Are you saying that the UA string begins with the literal text "User-Agent: "?
Yes. "User-Agent" is part of their UA string, which is what caused them to get blocked in the first place.
keyplyr
11:49 pm on Dec 25, 2013 (gmt 0)
Yes. "User-Agent" is part of their UA string, which is what caused them to get blocked in the first place.
ditto
dstiles
8:38 pm on Dec 27, 2013 (gmt 0)
My Christmas Eve posting was obviously a result of too much hurry (certainly not booze!). :(
Apart from mucking up a url (? thanks, phranque) I duplicated the IPs - they should differ in the final numerical subset - sorry, forget what it should be now. :)