This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10239 - How about using file-extensions instead of mime-types? It would allow application-specific files to be set as allowed.
Summary: How about using file-extensions instead of mime-types? It would allow applica...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-26 16:09 UTC by contributor
Modified: 2010-10-04 14:48 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-07-26 16:09:19 UTC 
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
Comment 1 Lachlan Hunt 2010-07-27 09:34:13 UTC 
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.
Comment 2 Ian 'Hixie' Hickson 2010-09-08 22:05:55 UTC 
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