Closed Bug 8443 Opened 21 years ago Closed 21 years ago

[Blocker]HTTP charset does not work

Categories

(Core :: Internationalization, defect, P3, blocker)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: ftang, Assigned: rpotts)

References

()

Details

Depend on Necko.
Blocks: 7228
Status: NEW → ASSIGNED
Target Milestone: M9
Depends on: 7232
No longer depends on: 7232
Chris,
Why did you remove the necko dependency?
We need netlib to parse the HTTP Content-Type header for the charset parameter
and set this info someplace (as libnet has done for years).  This is our
dependency on necko.

Then we need to grab that info, so that the appropriate converter will be
called if the HTTP Content-Type specifies a charset.
I created the test cases for Http charset in http://babel/tests/http_charset.html
Assignee: ftang → warren
Status: ASSIGNED → NEW
Target Milestone: M9 → M8
warran, plesae reassing this back to me after we can access the http header from
the caller when it became the default build. Please also supply how to access
information . Thanks.If possible, please mark the Target Milestone to a
reasonable one .Thanks. I need the "charset=" attribute from the "Content-Type"
header, if it exist.
Status: NEW → ASSIGNED
Target Milestone: M8 → M9
necko now lands in m9
Related to bug 11133.
Assignee: warren → rpotts
Status: ASSIGNED → NEW
bug 11133 is fixed now
This still does not work in 8-16 Win32, Mac, and Linux build.
Is this an M9 blocker?  If not please move to M10...if so, please mark blocker.
 Thanks!
Severity: normal → blocker
Summary: HTTP charset does not work → [Blocker]HTTP charset does not work
Target Milestone: M9 → M10
I move this to M10.  I put the broker for M10.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
I've added GetCharset() to nsIHTTPChannel...

-- rick
Status: RESOLVED → VERIFIED
I verified this in 9-10 Win32, Mac, and Linux build.
You need to log in before you can comment on or make changes to this bug.