- From: Malvoz <notifications@github.com>
- Date: Fri, 27 Jul 2018 15:53:55 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 27 July 2018 22:54:47 UTC
@MatteoWebDesigner The official media type for manifests is `application/manifest+json`, as long as you serve this media type you could have a manifest as a `.php` file for all that browsers care. If a developer doesn't have access to server configurations then `.json` would be the safest way to deploy the manifest. However as an **example** consideration for serving manifests with the `application/manifest+json` (which is default for `.webmanifest` but not for `.json` files) is under "Security and privacy considerations" in the spec: > ...because there is no way to prevent developers from including custom/unrestrained data in a manifest, implementors need to impose their own implementation-specific limits... There are probably alot of implications for serving a manifest with `application/manifest+json` rather than `application/json` and might the reason why `.webmanifest` exists so that (eventually) developers wont have to care about the server config because the correct media type is defined and so is default for the file extension. -- 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/689#issuecomment-408558218
Received on Friday, 27 July 2018 22:54:47 UTC