News for hackers. Stuff that matters.
Re:Favicon checker by gulpahum on Friday June 06, 2014 @07:44AM (#7857302)
I learned that IE11 looks for "browserconfig.xml" for pinned tile icons. So, if your site gets requests for that file, then blame IE11. Why Microsoft has to do this kind of crap?

"Note: If a webpage does not specify a browser configuration file, IE11 automatically looks for "browserconfig.xml" in the root directory of the server. To prevent this, use an "msapplication-config" header with the content attribute to "none" (shown earlier)." http://msdn.microsoft.com/en-us/library/ie/dn320426(v=vs.85)...

Re:Favicon checker by JohnTHaller on Friday June 06, 2014 @08:15AM (#7857399)
> Why Microsoft has to do this kind of crap?

Same reason Apple made up random image names for bookmark icons on the homescreen on the iPad and now they pollute our logs.

Re:Favicon checker by gulpahum on Friday June 06, 2014 @09:14AM (#7857641)
You are right. Apple is also bad.

The whole favicon retrieval seems to be a mess. I wish the W3C draft about manifests for web apps gets wide support and can be used on normal sites, too. (wishful thinking...?)

http://w3c.github.io/manifest/

Re:Favicon checker by davnola on Friday June 06, 2014 @12:53PM (#7859025)
Re:Favicon checker by Gracana on Friday June 06, 2014 @09:13AM (#7857635)
Why is this so bad?
Re:Favicon checker by chill1 on Friday June 06, 2014 @10:21AM (#7858009)
Because that's one more request that your web server will have to handle. And, if logging is enabled, each of those requests will create a log entry for the 404 error. And, apparently, to prevent the errant request from IE11, you have to add a specialized header for each response from your web server, requiring additional bandwidth of your web server and users.