Mike Helm wrote:

> One of my colleagues has found a recent bug in bugzilla on this
> https://bugzilla.mozilla.org/show_bug.cgi?id=399188 
> and  it appears that firefox is ignoring the mime type and
> looking at the .spc extension, and then dropping into
> Windows file management.  

I believe the present browser processing for files received via http
is something like this:

- if the MIME content type is known to the browser as a type it
handles internally, (either in native browser code, or through
extensions and add-ons/plugins) the browser handles the content
internally, otherwise ...

- If the MIME content type is known to be handled by another process
(e.g. MIME content type registered in Windows, or in the browser as a
"helper") then it is handled that way.  There may be a dialog involved
at this point.  Otherwise ...

- (on windows) the file name extension is looked up, and what ever
process is associated with that file name extension is run to handle it.
There may be a dialog involved at this step.

Note that there is a possibility that a file will be downloaded with
an unknown MIME content type, but when the file name extension is
looked up, the MIME content type associated with that extension will
be a type that is known to the browser.  In this case, one might
expect that the browser would handle the file internally, but it does
not.  This is a known bug, but I doubt that it's relevant to Thawte.

I suspect that Thawte is downloading the file with a content type that is
unknown to the browser, but is known to windows to be handled by
Windows' own cert manager.  I've seen that before.

-- 
Nelson B

_______________________________________________
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto

Reply via email to