Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Android Chrome Errors #360

Open
chrisbo opened this issue Feb 17, 2018 · 3 comments
Open

Android Chrome Errors #360

chrisbo opened this issue Feb 17, 2018 · 3 comments

Comments

@chrisbo
Copy link

chrisbo commented Feb 17, 2018

Is this a bug? The Web App Manifest and icons are definitely where they are supposed to be.
capture

@chrisbo
Copy link
Author

chrisbo commented Feb 17, 2018

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.

@phbernard
Copy link
Contributor

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?

@chrisbo
Copy link
Author

chrisbo commented Mar 1, 2018

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants