{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/manifest/issues/346","labels_url":"https://api.github.com/repos/w3c/manifest/issues/346/labels{/name}","comments_url":"https://api.github.com/repos/w3c/manifest/issues/346/comments","events_url":"https://api.github.com/repos/w3c/manifest/issues/346/events","html_url":"https://github.com/w3c/manifest/issues/346","id":65303272,"number":346,"title":"The use of the `.manifest` file extension may be problematic / confusing ?","user":{"login":"alrra","id":1223565,"avatar_url":"https://avatars.githubusercontent.com/u/1223565?v=3","gravatar_id":"","url":"https://api.github.com/users/alrra","html_url":"https://github.com/alrra","followers_url":"https://api.github.com/users/alrra/followers","following_url":"https://api.github.com/users/alrra/following{/other_user}","gists_url":"https://api.github.com/users/alrra/gists{/gist_id}","starred_url":"https://api.github.com/users/alrra/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alrra/subscriptions","organizations_url":"https://api.github.com/users/alrra/orgs","repos_url":"https://api.github.com/users/alrra/repos","events_url":"https://api.github.com/users/alrra/events{/privacy}","received_events_url":"https://api.github.com/users/alrra/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-03-30T21:10:59Z","updated_at":"2015-04-02T21:03:05Z","closed_at":null,"body":"\r\nFrom: http://w3c.github.io/manifest/#h-media-type-registration\r\n\r\n```\r\nFile extension(s):\r\n    .json, .manifest\r\n```\r\n\r\n`.manifest` was the recommended file extension for the [Application Cache manifest file](https://html.spec.whatwg.org/multipage/browsers.html#manifests), and then, it was changed to  `.appcache` in order to [_\"avoid clashing with Microsoft's unregistered `application/manifest` type\"_](https://html5.org/r/5812). \r\n\r\nSo, taking into consideration also the [legacy](https://www.google.com/search?hl=en&q=%22addtype+text%2Fcache-manifest+manifest%22) aspects, recommending `.manifest` as the file extension creates even more \"clashing\", and this can complicate things when it comes to server configs (e.g.: especially as in some of the cases, things like the media type [matter](https://developer.mozilla.org/en-US/docs/Web/HTML/Using_the_application_cache#Referencing_a_cache_manifest_file)).\r\n\r\n__Note:__ As opposed to `.manifest`, in the case of `.json`, IMHO, things are better. Since for the manifest files for web apps the media type doesn't seem to matter (for now at least), and they are just JSON files, the configurations that most servers out there have should already work great for them (e.g.: serve them compressed, with the media type [`charset` parameter](http://www.w3.org/International/O-HTTP-charset#charset) set to `utf-8`, etc.).\r\n\r\n---\r\n\r\nI've open this issue because I didn't find any previous discussion on this. I do apologize in advance if I missed something.\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/w3c/manifest/issues/comments/89043694","html_url":"https://github.com/w3c/manifest/issues/346#issuecomment-89043694","issue_url":"https://api.github.com/repos/w3c/manifest/issues/346","id":89043694,"user":{"login":"alrra","id":1223565,"avatar_url":"https://avatars.githubusercontent.com/u/1223565?v=3","gravatar_id":"","url":"https://api.github.com/users/alrra","html_url":"https://github.com/alrra","followers_url":"https://api.github.com/users/alrra/followers","following_url":"https://api.github.com/users/alrra/following{/other_user}","gists_url":"https://api.github.com/users/alrra/gists{/gist_id}","starred_url":"https://api.github.com/users/alrra/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alrra/subscriptions","organizations_url":"https://api.github.com/users/alrra/orgs","repos_url":"https://api.github.com/users/alrra/repos","events_url":"https://api.github.com/users/alrra/events{/privacy}","received_events_url":"https://api.github.com/users/alrra/received_events","type":"User","site_admin":false},"created_at":"2015-04-02T21:03:05Z","updated_at":"2015-04-02T21:03:05Z","body":"> Should we just call it .webmanifest? I think anything we come up with is going to be terrible \r\n\r\n@marcoscaceres Having a unique file extension would make things very easy in terms of server configs, so :+1: for that.\r\n\r\n>  (and not send the recommended mime type). \r\n\r\nIt's not only about _\"sending the recommended mime type\"_. Some servers (e.g.: Apache) rely on the media type for different settings (e.g: [ExpiresByType](http://httpd.apache.org/docs/current/mod/mod_expires.html#expiresbytype)), and not having a unique file extension sometimes makes the mapping to a media type [not so straightforward](https://github.com/h5bp/server-configs-apache/blob/9336f201aa1664ac0c9b76442ba354c3a38bcbf6/dist/.htaccess#L186-L217).\r\n\r\n>   and 99% of people will just use .json\r\n\r\nThe HTML5 Boilerplate project is [looking into adding a starter web application manifest file](https://github.com/h5bp/html5-boilerplate/pull/1629), and some of the H5BP server configs had some default configs for this [for quite some time](https://github.com/h5bp/server-configs-apache/issues/29), so if something changes regarding the file extension, we'll try to help even more (e.g.: recently we removed the `.manifest` → `text/cache-manifest` mapping from all our server configs: [1](https://github.com/h5bp/server-configs-apache/commit/c805353c4142c792267945687309259fc15b2106), [2](https://github.com/h5bp/server-configs-nginx/commit/d7e0e1bf46c89e387b201d849711ff8564e9652e), [3](https://github.com/h5bp/server-configs-gae/commit/584759ec0e1fe166cc96b36e6ff00c91769712e0), [4](https://github.com/h5bp/server-configs-lighttpd/commit/27ff0ab0b82aeb63d954294944af956c9ad5d4a6)).\r\n"}}