Docs suggestion: PWA .webmanifest files often served as HTML

[skaffa]

Description

Many modern web apps use PWA manifests (.webmanifest).
On common PHP setups, these are often routed through PHP and returned as HTML, silently breaking PWA installability.
Would it make sense to:

• Document .webmanifest as a JSON resource, or
• Recommend default MIME mappings (application/manifest+json), or
• Provide guidance for common servers (Apache/nginx) in the PHP docs?

[iluuu1994]

Hi @skaffa

Provide guidance for common servers (Apache/nginx) in the PHP docs?

Wouldn't you expect to find this in the Apache or nginx documentation then? I don't think PHP should hard-code content-types based on URLs. Such a change would likely require a discussion on the internals mailing list.

[skaffa]

It's not necessarily a URL, but rather the extension, being webmanifest, which would be safe to handle as JSON due to it being oddly specific to its purpose.

[iluuu1994]

Right, but where do we stop? Why does .webmanifest get an auto-content-type, but .json, .txt, .pdf, .docx etc. don't? It just seems like an odd exception to make. As far as documentation goes, where would we add this? Doesn't seem like there's an obvious place where this would be discovered by users who would find it useful.

[NattyNarwhal]

We do have the SAPI dev server, and that does actually have webmanifest in the list for MIME types. For production web servers, Apache and nginx don't seem to have webmanifest in their default mime types, so it'd probably be best to the make changes over there.