Bug 20726
| Summary: | File upload failing to set Content-Type: application/octet-stream | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | M Schneider <mlschneider> |
| Component: | Forms | Assignee: | Nobody <webkit-unassigned> |
| Status: | UNCONFIRMED | ||
| Severity: | Normal | CC: | cuchaz |
| Priority: | P2 | ||
| Version: | 525.x (Safari 3.1) | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| URL: | http://code.google.com/p/chromium/issues/detail?id=1269 | ||
M Schneider
Submitting an
input type="file"
with an unknown binary file type results in the server not handling the file correctly.
This appears to be an issue on Windows where MIMETypeRegistry::getMIMETypeForExtension doesn't return a default of
"application/octet-stream" when the MIME type is unknown.
This results in no Content-Type line being sent to the server, which in turn keeps the server from processing the file properly.
The file type that originally experienced this issue was a dbase III+ dbf. See the url for a sample file.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Jon@Chromium
Also reported to chromium. http://code.google.com/p/chromium/issues/detail?id=1269
Cuchaz
This is also a problem in Google Chrome for linux, so it might not be a windows-only issue. On the server side, Struts2 thinks the content-type is null for such files. I'm not sure what headers are actually being sent.