When a single site has multiple hostnames (e.g. www.example.com and www-cms.example.com), a race condition occurs in which the first hostname served is used for all hostnames. This can cause retrieval of the manifest file to result in a CORS error.
Using the previous example, if the first page load is for www-cms.example.com, then pages loaded from www.example.com will have their favicon links rendered to load from www-cms.example.com
To be clear, the www and www-cms sites are meant to be serving the same content. In my particular use case, www is intended to be accessed by the general public while www-cms is used to edit site content.
www.example.com and www-cms.example.comThe favicon links on www.example.com will reflect www-cms.example.com.
I believe this can be remedied by setting the cache context to 'url.site'.
None
None
None
Active
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
A patch for this issue. The approach is to vary the cache-id to distinguish between sites. This causes the favicon paths to mirror the hostnames they'll be retrieved from (e.g. https://example.com vs https://www.example.com) and avoid CORS errors on any manifest files.