Will Browsers Request /favicon.ico Or First?
I want to set a favicon to be requested from a static file server instead of the main web server for performance optimization.
If I specify a <link rel="shortcut icon" target="_blank" rel="nofollow noreferrer" href="http://cdn.site.com/favicon.ico"> but also have a /favicon.ico in my site root as a fallback, which will browsers prefer? Will browsers (and which?) still look for /favicon.ico, making the move to a static file server useless?
Answer
I did the test suggested above. I placed a /favicon.ico in the root of a domain, and a link, and fired up the page in:
- Opera 10
- Opera 9.64
- Firefox 3.5
- IE 6
- IE 7
- IE 8
- Safari 4
They all showed the icon loaded with <link rel="shortcut icon" target="_blank" rel="nofollow noreferrer" href="http://cdn.site.com/favicon.ico"> (located on an external server). I checked access.log, and there were no requests to /favicon.ico!
I then commented out the <link>, checked again in all browsers, and they showed the /favicon.ico icon and corresponding entries in access.log.
Related Questions
- → How to access the Visual interface for October?
- → How to implement DbDongle::convertTimestamps as workaround of invalid timestamps with MySql strict
- → Laravel 5: Apache php http authentication
- → Trait 'IlluminateFoundationBusDispatchesJobs' not found
- → Disable CSRF TokenMismatch for specific routes on Lumen
- → Change fill color of d3.js node
- → Authenticate with a cookie using laravel 5.1 and jwt
- → What is causing the web page to reload?
- → Is there any way to make an SVG object clickable?
- → Keeping uploaded files secure but still available via https
- → CORS missmatch because of http
- → 500 Internal Server Error Ajax Laravel
- → React: How to publish page on server using React-starter-kit