Re: [w3c/manifest] Support a way to update explicitly (#446)

@aarongustafson we are shipping an app as static files through Netlify, and we serve it from multiple domains, where it customizes itself with different names, logos and theme colors depending on the host. The app gets the host from the client and tells the server where it is running. The server do not have other way to have this information because calls to the server are proxied through Netlify so all calls seems to come from them. 

This works wonders in every aspect since all network calls are controlled by javascript and we can easily inject a custom header with the host. The only requests we can’t control this way are the favicon and manifest since the app does not know the host where it’s running until runtime. We checked and the favicon could be loaded dynamically inserting the link tag in head with a parameter signaling the host to the server, but it seems we cannot do the same for the manifest.

I think it would be enough and expected by users if it worked as the favicon tag and we could insert it on runtime. I suppose there is no widely supported workaround right now, but if there are any suggestions I would love to hear them. Thanks.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/446#issuecomment-498968939