Forum Moderators: DixonJones

Message Too Old, No Replies

Multiple Requests For favicon.ico

         

piskie

12:20 am on Apr 2, 2011 (gmt 0)

10+ Year Member



At the turn of the year, a series of multiple requests from a different IP each time started requesting favicon.ico
For example:
75.101.222.128 - - [01/Feb/2011:08:20:28 +0000] "GET /favicon.ico HTTP/1.1" 200 2822 "-" "-"
This request ran over 1,000 times in a 3 hour slot each request from a different IP.

Do I need to worry, and how can I stop these requests without interfering with the site functionality?
I would prefer them to not appear as 200s in my logs if it is possible.
Can anybody shed any light on this please.

piskie

10:32 pm on Apr 4, 2011 (gmt 0)

10+ Year Member



Anybody have any suggestions ?

enigma1

10:25 pm on Apr 22, 2011 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I get them a lot, requests just for the favicon and not a single page request. They're accompanied by some spammy referrer, they hope the server logs may appear somewhere in public, in which case the spammer benefits from the referrer best case scenario a link exposure.

Remove the favicon.ico from the site(s) and use a different name for the icon. (for instance example.ico) and make sure it is included in the html pages. Add a rule to the server config like .htaccess to do something with the favico.ico if you want to play around.

I tested several things including issuing redirects across multiple domains in many cases they followed - not much happened other than keep bouncing back and forth - but use your seo imagination. Or just use a 404 rule if you don't have time to play.

In general accesses to the html side resources (css, icons, js etc) are totally transparent to the end user as the browser doesn't bother to report anything and what's going on in the background is another story as you're discovering via the server logs along with the possible "applications".

piskie

10:29 am on Apr 23, 2011 (gmt 0)

10+ Year Member



Thanks enigma.
That confirms more or less my conclusions. However, not being the best implementer of htaccess tis probably prudent for me to let them run with it. If I try to get too clever for my own ability, I could torpedo some genuine visitors.