I have my own domain and want to change the favicon to an SVG file. I've tried several solutions regarding syntax etc. but no joy. Discovered that Safari saves this information in a SQLite database, but changing my HTML code doesn't have any effect. Why would Safari want to have a persistent reference to something belonging to my web site. It's my code.
iMac 24″, macOS 15.7
Chances are the data is cached. If Safari originally downloaded the favicon, and the server set a far-future expiration date, then Safari will assume the version is has is still valid and won't bother downloading the new one.
Every HTTP response has an optional expiration date, and Safari is just doing what it's told.
Unfortunately, it's not easy to find out the cache expiration of existing content (it's stored within the database and you'd need to query it directly).
Unfortunately, since the filename is fixed, it's not as simple as changing the filename, which is the classic way of expiring content (just tell the web browser a new file name that it hasn't seen before and cannot have cached).
Thank you for this response. It does explain some of the actions involved, but leaves me still scratching my head. Firefox immediately rendered the new favicon after a page refresh. Why can't Safari?
My understanding is that Safari does save the favicon (as well as much more data) in ~/Library/Safari. I've seen the database and other files. But my question is why would a browser save anything like that at all in a database?. It's like content on a web page - put it in a cache and allow me to clear that out once in a while.
Safari not updating SVG favicon after HTML changes
