Forum Moderators: open

Message Too Old, No Replies

Jigsaw

         

wilderness

2:00 am on Oct 11, 2009 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Interersting how neither the "Jigsaw" or "Validatior" UA's are allowed and the middle result is a blank UA from a host with known vulnerbilities.

128.30.52.nn - - [10/Oct/2009:15:10:58 +0100] "GET / HTTP/1.1" 403 1159 "-" "Jigsaw/2.2.5 W3C_CSS_Validator_JFouffa/2.0"
128.30.52.nn - - [10/Oct/2009:15:10:59 +0100] "GET / HTTP/1.1" 403 1159 "-" "W3C_Validator/1.654"
97.74.144.nnn - - [10/Oct/2009:15:11:01 +0100] "GET / HTTP/1.1" 403 1159 "-" "-"
97.74.144.nnn - - [10/Oct/2009:15:11:02 +0100] "GET / HTTP/1.1" 403 1159 "-" "-"
128.30.52.nn - - [10/Oct/2009:15:11:02 +0100] "GET / HTTP/1.1" 403 1159 "-" "Jigsaw/2.2.5 W3C_CSS_Validator_JFouffa/2.0"
128.30.52.nn - - [10/Oct/2009:15:11:02 +0100] "GET / HTTP/1.1" 403 1159 "-" "Jigsaw/2.2.5 W3C_CSS_Validator_JFouffa/2.0"

[edited by: incrediBILL at 8:25 pm (utc) on Oct. 29, 2009]
[edit reason] Obscured IPs [/edit]

incrediBILL

8:25 pm on Oct 29, 2009 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Don, I don't see the relevance between the MIT.edu IPs and the ones from GoDaddy Servers.

I think it's a coincidence because there's no reason a CSS validator would need to ping your site in other ways as they don't care about cloaking.