Closed Bug 22321 Opened 25 years ago Closed 25 years ago

URI dispatcher needs to discern content-type

Categories

(Core :: Networking, defect, P3)

Product:
Core
Component:
Networking
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: jud, Assigned: jud)

References

(
URL
)

Details

If the channel being loaded doesn't have a content-type, we need to be scanning
the first X bytes of the stream somehow to determine content type. The listed
url redirects to a cgi that generates html, but we throw a unknown content type
handler dialog instead.
*** Bug 21055 has been marked as a duplicate of this bug. ***
Rick, should I re-assign this to you since you added the code to sniff for a
content type to the uri loader the other day? (I think I saw that that stuff landed)
Assignee: mscott → rpotts
This is something Rick Potts has been cooking up. I think it is partially baked
already in the uriloader. Re-assigning to him.
Assignee: rpotts → valeski
Target Milestone: M14
Rick is out on vacation for 2 weeks. Reassigning to Jud.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
this has been fixed. for text/plain and test/html
verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.