184971 - display MIME type of the server in download dialog and not the mime-type returned by windows registry

Ralf Hauser

Reporter

Description

•

23 years ago

see description in above bug

benc

Comment 1

•

23 years ago

-> file handling

Assignee: dougt → law

Component: Networking → File Handling

QA Contact: benc → petersen

Boris Zbarsky [:bzbarsky]

Comment 2

•

23 years ago

Um... We _DO_ show the server-provided type in the download dialog. We have specific code to do so, and have for years -- see http://lxr.mozilla.org/seamonkey/source/uriloader/exthandler/nsExternalHelperAppService.cpp#288 So the question is, what's really going on here. Is there a URL I can hit to actually see what the server is sending? What is the server expected to be sending?

Nelson Bolyard (seldom reads bugmail)

Comment 3

•

23 years ago

No, the problem is that the windows registry maps the server's download MIME content type to a file name extension, which in turn gets mapped to another MIME content type. The dialog shows the content type to which the file name extension is mapped, not the content type that was originally presented by the server. This is all explained in http://bugzilla.mozilla.org/show_bug.cgi?id=184052#c11 and in the attachment http://bugzilla.mozilla.org/attachment.cgi?id=108984&action=view The server downloaded MIME type application/pkix-cert. On Win2k, that maps to file name extension .cer, which maps to MIME type application/x-x509-CA-cert. As shown in the attachment cited above, the mozilla dialog shows application/x-x509-CA-cert, but it should show application/pkix-cert. The problem with showing the wrong MIME type is that it confounds any attempt to diagnose misbehavior. mozilla recognizes and deals with the MIME type application/x-x509-CA-cert when the server provides that type. But when the server provides a type unknown to mozilla, the user gets the dialog cited in the attachment above. So, when the dialog states that the MIME type was one that mozilla recognizes, it leaves everyone wondering why in the heck did mozilla show this dialog? The reader of the dialog is not able to diagnose the real problem, which is that the server used a MIME type that mozilla does not recognize. The URL with which this was originally seen was http://bugzilla.mozilla.org/show_bug.cgi?id=184052#c11 I don't know if that URL still acts as before or not, but even if it does not, this bug is valid and needs to be fixed.

Boris Zbarsky [:bzbarsky]

Comment 4

•

23 years ago

Ok, I finally hunted this down. This is a Windows-specific bug that only pops up when a type is mapped to an extension but the extension is mapped to a different type (which is why it never came up before). The code mentioned in comment 2 would not cover this case.

Boris Zbarsky [:bzbarsky]

Comment 5

•

23 years ago

This will be fixed, basically, once bug 178122 is resolved. For the record, the issue is that GetFromMIMEType on Windows sets the wrong MIME type in the MIMEInfo (!) and the main helper app service code does not expect such idiocy.

Boris Zbarsky [:bzbarsky]