Open chrisbo opened 6 years ago
I ended up resolving all three issues myself by adding the .webmanifest mime type application/manifest+json without fully looking into the implication of doing so. Feedback welcome.
Hum... not good. Retro compatibility was a question before changing the name and extension of the manifest.
Before you upgraded the mime type, what was happening when accessing https://www.figtreehotel.com.au/site.webmanifest ? Was the server sending the manifest? With which (default) mime type? You are using Microsoft-IIS, correct?
Couldn't remember, so just removed it to test and this was the response...
HTTP/1.1 404 Not Found => Content-Type => text/html Server => Microsoft-IIS/10.0 X-Powered-By => ASP.NET Date => Thu, 01 Mar 2018 16:13:33 GMT Connection => close Content-Length => 103
Is this a bug? The Web App Manifest and icons are definitely where they are supposed to be.