729600 - mime type issue, truncated contentsubtype on upload of pdf as text/xm

Status: RESOLVED DUPLICATE of bug 373621

(Core :: General, defect)

Description

[Bob Imperial]

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2
Build ID: 20120215223356

Steps to reproduce:

Uploading a pdf document using Firefox 10.0.2 


Actual results:

upon upload I encountered "The MIME type of the uploaded file text/xm was not accepted by the server. " using an upload tool that's been working fine for a few years now. Tested using IE and Safari as well without issue on WinXP SP3


Expected results:

well, in short the file should have uploaded. Can test for yourself here:
http://domint.med.unc.edu/test/index.cfm

Comment 1

[Bob Imperial]

Tested this on an earlier version, 9 and it works fine fyi.

Comment 2

[Boris Zbarsky [:bzbarsky]]

The MIME type sent will depend on your OS configuration and your helper application settings.  For example, for me it sends "application/x-pdf", which the site likewise does not accept.

That said, if 9 is using the same profile you should get the same behavior.  _Are_ you using the same profile with 9?

Comment 3

[Bob Imperial]

the testing with version 9 was done on a completely different box so no the profiles were not the same. As for the OS config and mime types, the box this is on is set to accept "application/pdf" which as I mentioned has worked fine for a few years now with not change. The URL I supplied was for a bare-bones upload tool out of the context of any application scope so I could rule out any issues with application coding.

Comment 4

[Boris Zbarsky [:bzbarsky]]

What does the mimeTypes.rdf in your profile have to say for the "text/xm" MIME type or the "pdf" extension?

Comment 5

[Bob Imperial]

the first shows:
  <RDF:Description RDF:about="urn:mimetype:handler:text/xm"
                   NC:alwaysAsk="true"
                   NC:useSystemDefault="true"
                   NC:saveToDisk="false">
    <NC:externalApplication RDF:resource="urn:mimetype:externalApplication:text/xm"/>
  </RDF:Description>

for pdf it shows:
  <RDF:Description RDF:about="urn:mimetype:handler:application/pdf"
                   NC:alwaysAsk="true"
                   NC:useSystemDefault="true"
                   NC:saveToDisk="false">
    <NC:externalApplication RDF:resource="urn:mimetype:externalApplication:application/pdf"/>
  </RDF:Description>

Comment 6

[Bob Imperial]

shouldn't the text/xm be text/xml ?

Comment 7

[Boris Zbarsky [:bzbarsky]]

> for pdf it shows:

I was asking about entries that contain NC:fileExtensions="pdf".  Note that there might be more than one.

> shouldn't the text/xm be text/xml ?

That depends.  Entries in this file can come from types you've encountered on the web, so if someone sent text/xm, you can get a text/xm in this file.

Comment 8

[Bob Imperial]

  <RDF:Description RDF:about="urn:mimetype:application/pdf"
                   NC:fileExtensions="pdf"
                   NC:description="Adobe Acrobat Document"
                   NC:value="application/pdf"
                   NC:editable="true">
    <NC:handlerProp RDF:resource="urn:mimetype:handler:application/pdf"/>
  </RDF:Description>

Comment 9

[Boris Zbarsky [:bzbarsky]]

That's the only entry with NC:fileExtensions="pdf"?

Comment 10

[Bob Imperial]

my bad, trying to get some coding done here meanwhile; 

  <RDF:Description RDF:about="urn:mimetype:text/xm"
                   NC:fileExtensions="pdf"
                   NC:description="Adobe Acrobat Document"
                   NC:value="text/xm"
                   NC:editable="true">
    <NC:handlerProp RDF:resource="urn:mimetype:handler:text/xm"/>
  </RDF:Description>

Comment 11

[Boris Zbarsky [:bzbarsky]]

OK, that's what's going on.  Some file you dealt with had the extension "pdf" and the type "text/xm" and we remembered that file association...

There's an existing bug on that; in the meantime just deleting the text/xm stuff from that file while your browser is not running will help.