Closed Bug 279619 Opened 20 years ago Closed 19 years ago

file upload via POST presents an incorrect mime type to server

Categories

(Firefox :: File Handling, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 373621

People

(Reporter: tom_wilde, Assigned: bugs)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041020 Firefox/0.10.1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041020 Firefox/0.10.1 ETHEREAL SESSION GRAB --------------------- Basically the bug is this: I'm uploading a PDF file to the server but Firefox thinks my file is a gif [it's not] excerpt from below: Content-Disposition: form-data; name="upload_file"; filename="11_04.2.pdf" Content-Type: image/gif thought you guys should know.. POST /KPMG_Project_1/respondDocumentAdd HTTP/1.1 Host: localhost:8080 User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041020 Firefox/0.10.1 Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Referer: http://localhost:8080/KPMG_Project_1/view_document_add Cookie: tree-s="eJzTyCkw5NLIKTDiClZ3hANXW3WuAmOuxEQ9AIOOB9Q"; _ZopeId="26516302A1rEO5LfwMw"; _DFE_expert="0"; _DFE_filter="" Authorization: Basic YWRtaW46YWRtaW4= Content-Type: multipart/form-data; boundary=---------------------------16503769819736174781113397361 Content-Length: 11877702 -----------------------------16503769819736174781113397361 Content-Disposition: form-data; name="return_url" http://localhost:8080/KPMG_Project_1 -----------------------------16503769819736174781113397361 Content-Disposition: form-data; name="progressor_id" -----------------------------16503769819736174781113397361 Content-Disposition: form-data; name="upload_file"; filename="11_04.2.pdf" Content-Type: image/gif %PDF-1.4%.... 1185 0 obj<< /Linearized 1 /O 1189 /H [ 1778 927 ] /L 11876317 E 3164233 Reproducible: Always Steps to Reproduce: sorry - found this on a closed system, however it should be easy enough to reproduce with a simple page and ethereal to grab the session Actual Results: During a HTTP POST: Content-Disposition: form-data; name="upload_file"; filename="11_04.2.pdf" Content-Type: image/gif pdf != gif sorry! Expected Results: pdf == pdf zope was the backend but since this was a POST that should matter...
I've also had similar problems, also uploading to a Zope server. IE works fine, so it's not the server. I originally reported this under 288793 but this report is a much better fit. After upgrading from Firefox 1.0.3 to 1.0.4 with Windows XP I have problems uploading pdf files to my website. The website runs Plone, a CMS. I upload to a "File" content type and the site is supposed to detect the mime type and save it with the file. With an upload from Firefox it's detecting "text/unknown". With Internet Explorer it detects "application/pdf". This causes all sorts of problems when the site displays it, but that's not the issue here.
Here's a fix, but I don't know why it happened. In a file called C:\Documents and Settings\????\Application Data\Mozilla\Firefox\Profiles\default.qcm\mimeTypes.rdf I found this entry: <RDF:Description RDF:about="urn:mimetype:text/unknown" NC:value="text/unknown" NC:editable="true" NC:fileExtensions="pdf" NC:description="Adobe Acrobat Document"> <NC:handlerProp RDF:resource="urn:mimetype:handler:text/unknown"/> </RDF:Description> I changed it to: <RDF:Description RDF:about="urn:mimetype:application/pdf" NC:value=" application/pdf " NC:editable="true" NC:fileExtensions="pdf" NC:description="Adobe Acrobat Document"> <NC:handlerProp RDF:resource="urn:mimetype:handler: application/pdf "/> </RDF:Description> Then, after I had restarted Firefox, the uploads worked properly again. I don't know how this entry got there.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Resolution: EXPIRED → DUPLICATE
You need to log in before you can comment on or make changes to this bug.