Forum Moderators: DixonJones
216.174.233.25 - - [05/Oct/2002:05:55:51 -0400] "GET /notsonice/19.jpeg HTTP/1.1" 404 219 "http://www.not-so-nice1.com/notsonice/" "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)"
216.174.233.25 - - [05/Oct/2002:05:55:53 -0400] "GET /thumbs/10248.JPEG HTTP/1.1" 404 223 "http://www.not-so-nice2.com/thumbs/" "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)"
216.174.233.25 - - [05/Oct/2002:05:55:58 -0400] "GET /thumbs/10246.JPEG HTTP/1.1" 404 223 "http://www.not-so-nice2.com/thumbs/" "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)"
My concern is...I hope to eventually convert my site to a greeting card site that will be kid safe. I looked up the whois record and neither of these "not-so-nice" domains appear to be hosted by my server who's policy is to not host "not-so-nice"sites (Thank God!), but how could a different domain request show up in my logs? Could this be "Gator" or some other ad parasite latching onto my domain....OR did some internet wires get crossed?
see: [thiefware.com...]
The reason I'm thinking it might be an ad parasite is because a friend of mine is seeing popups from her professional site from her browser at home. These popups appear to be generated from her site - when they're not. They're actually generated by the user's browser by some ad software that most of the time people are unaware that they've even downloaded. Similar to the Gator software that is generating FedEx popup ads from the UPS site.
Someone - or something IS hitting your server asking for these files - whether or not they exsist. The question is why?
We will probably never know for sure and any guess is as good as mine - so Iĝll just leave it with the (good) ones that has come up.
If the requests bothers you block the agent or IP and get on with something more fun :)
"This looks like someone probing to see if they could exploit the site as an anonymous open proxy. Notice the result codes are all 404. If the proxy was vulnerable the response would show '200' or 'OK'. Nothing to worry about here."
I haven't a clue what this means (anonymous open proxy) - but I guess it's not a problem.
If the proxy was vulnerable the response would show '200' or 'OK'.
I hope this isn't true. I get hits asking for other domains (usually yahoo or google) that return 200's.
From what I understand, apache tries to match these domains to a virtual host. If one is not found it defaults to your main site. Therefore you get a 200 OK code, but the person is just seeing your homepage.
If a 200 means your server is misconfigured to act as an anonymous proxy, I'm in trouble!