144675 - Stream converter service needs to be smarter about mime types

Status: VERIFIED WORKSFORME

(Core :: Networking, defect, P3)

Description

[Boris Zbarsky [:bzbarsky]]

From bug 86835, comment 21:

  is there a bug to track the 'global issues' that the stream converter service
  is not  parsing the content-type correctly and is too simplistic in the way it
  chooses converters ??

This is such a bug, since I could find no existing bug on it.

Comment 1

[Doug Turner (:dougt)]

are there specific bugs that you can enumerate?

Comment 2

[Boris Zbarsky [:bzbarsky]]

Not that are filed... but here's a typical example.

"application/x-unknown-content-type; x-view-mode=view-source"

The current mechanism would not run this through the unknown decoder, since it
does not match the "application/x-unknown-content-type" string that decoder is
registered for.  Or say some site sends content with:

Content-Type: application/binhex; details="none"; charset="something"

We would not run that through the binhex converter, though arguably we should.

Comment 3

[Boris Zbarsky [:bzbarsky]]

I should just take this.

Comment 4

[Boris Zbarsky [:bzbarsky]]

So... per the comments in nsIChannel.idl, this bug seems invalid.  Any channel
that does what the view-source channel was doing is violating the nsIChannel
interface definition.

Comment 5

[Darin Fisher]

right, marking WORKSFORME

Comment 6

[benc]

VERIFIED/wfm, per bz & darin.