10239 2010-07-26 16:09:19 +0000 How about using file-extensions instead of mime-types? It would allow application-specific files to be set as allowed. 2010-10-04 14:48:56 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#file-upload-state P3 normal --- 1 contributor ian ian julian.reschke mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 37101 0 contributor 2010-07-26 16:09:19 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#file-upload-state Comment: How about using file-extensions instead of mime-types? It would allow application-specific files to be set as allowed. Posted from: 62.162.198.38 37105 1 lachlan.hunt 2010-07-27 09:34:13 +0000 No, the file name extension is largely irrelevant in an HTTP context. While there are some conventions, there are many file extensions that just don't say anything about the file type. e.g. .php, .cgi, .pl, etc. Such resources can return content of any type. 38697 2 ian 2010-09-08 22:05:55 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: see comment 1