Requests to /favicon.ico consistently returns the Subversion favicon.ico but I can't find the configuration resulting in this

Question

On one of my servers which is being used for some internal development spaces and the likes, are configured with Apache, Git, Subversion among other things. The VirtualHost configuration is nothing out of the ordinary and I thought I had full control and understanding of this server's configuration and how it runs. I guess I was wrong. I recently discovered that all requests, no matter what VirtualHost I try, return the Subversion favicon when accessing <vhost>.<domain>/favicon.ico. This puzzled me - and annoyed me a bit since I was convinced that I knew all about this server's configuration.

It doesn't seem to pose any problems but I'm annoyed that there is a configuration somewhere which does something I explicitly didn't ask for. So I've been trying to track down this configuration but so far with no luck.

The server is running Gentoo Linux, so I figured I was looking for a <Location> block somewhere in my Apache configuration. I've been going through all my VirtualHost definitions, all my module configurations and my Apache configuration. I've even gone so far as to grep for all <Location> and favicon entries in all of my /etc/ files. Still no luck.

I've run out of ideas as to how I'm going to hunt down this thing so I'm hoping for some help from you guys and girls.

Thank you for your time :)

Answer 1

Okay, I'm a bit wiser. It's a slow day at the office so I have some time to spend on this little detail :)

I now know where the favicon.ico is coming from - I think.

In my server's /var/www/localhost/htdocs/ is a favicon.ico which for some reason unknown to me is the Subversion logo. If I rename this file, all suddenly works and it correctly grabs the favicon I have placed for each VirtualHost.

That's nice but I'm still quite puzzled as to why that hosts favicon took precedence over the individual VirtualHosts favicon. I still can't seem to find any <Location> definitions in any of the VirtualHosts which could lead to this behaviour.