If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Document when nsIChannel::contentType is available

NEW
Unassigned

Status

()

Core
Networking
P3
enhancement
12 years ago
11 days ago

People

(Reporter: Biesinger, Unassigned)

Tracking

Trunk
Points:
---
Bug Flags:
blocking1.9 -
wanted1.9 +

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [necko-backlog][good first bug], URL)

Currently, nsIChannel.idl avoids the question when the contentType is available.
It also does not say what happens if the type is not known.

It should document that the type is available in and after onStartRequest (or
after open()). I'm not sure what we do for an unknown type, I think we may
return "application/x-unknown-type" or somesuch...
Flags: blocking1.9a1?

Updated

11 years ago
Assignee: darin → nobody
QA Contact: benc → networking
Flags: blocking1.9a1? → blocking1.9-
Whiteboard: [wanted-1.9]
Flags: wanted1.9+
Whiteboard: [wanted-1.9]
Whiteboard: [necko-backlog][good first bug]
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
You need to log in before you can comment on or make changes to this bug.