The default bug view has changed. See this FAQ.

[FEATURE] libmime needs a way to detect the charset of the destination webshell (if available)

VERIFIED FIXED in M11

Status

()

Core
Networking
P3
normal
VERIFIED FIXED
18 years ago
18 years ago

People

(Reporter: rhp (gone), Assigned: Warren Harris)

Tracking

Trunk
x86
Windows NT
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
After a newsgroup discussion, warren posted:

 > I'm not sure how you should get the webshell from libmime. This
 > is probably related to the infamous "event sink getter" architecture
 > that is yet to be determined. I want to do that next (for m10).

So I want to make sure we track this as we move towards beta.

Updated

18 years ago
Blocks: 5938

Updated

18 years ago
Target Milestone: M10

Comment 1

18 years ago
I marked this M10 per the comments above and to get off the 'Necko, no
milestone' radar. Feel free to change.
(Assignee)

Updated

18 years ago
Status: NEW → ASSIGNED
(Assignee)

Comment 2

18 years ago
Gagan, should this be an accessor on nsIChannel? Or should it be an event sink?

Comment 3

18 years ago
Rick said that he was going to add it nsIHTTPChannel. It doesn't make sense to
do it to nsIChannel. But for the moment if you need to parse out the charset,
you can see anything after the semicolon on a
nsIHTTPChannel::GetResponseHeader("Content-Type", &foo); which is the raw HTTP
header as compared to the nsI[HTTP]Channel::GetContentType() call. Cc'ing
rpotts.
(Assignee)

Updated

18 years ago
Blocks: 12839

Comment 4

18 years ago
Spoke with warren at bug triage today.  Not an M10 blocker...moving to M11.
(Assignee)

Updated

18 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
(Assignee)

Comment 5

18 years ago
Looks like this has already been done. nsIHTTPChannel::GetCharset

Updated

18 years ago
Status: RESOLVED → VERIFIED

Comment 6

18 years ago
I trust warren, marking verified for tracking purposes.

Comment 7

18 years ago
Bulk move of all Necko (to be deleted component) bugs to new Networking

component.
You need to log in before you can comment on or make changes to this bug.