Closed Bug 144675 Opened 23 years ago Closed 22 years ago

Stream converter service needs to be smarter about mime types

Categories

(Core :: Networking, defect, P3)

Product:
Core
Component:
Networking
Type:
defect

Tracking

()

Status:
VERIFIED WORKSFORME
Milestone:
mozilla1.7beta

People

(Reporter: bzbarsky, Assigned: bzbarsky)

Details

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.
Keywords: helpwanted
are there specific bugs that you can enumerate?
Target Milestone: --- → Future
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.
I should just take this.
Assignee: new-network-bugs → bzbarsky
Keywords: helpwanted
Priority: -- → P3
Target Milestone: Future → mozilla1.7beta
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.
right, marking WORKSFORME
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
VERIFIED/wfm, per bz & darin.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.