Closed
Bug 8443
Opened 25 years ago
Closed 25 years ago
[Blocker]HTTP charset does not work
Categories
(Core :: Internationalization, defect, P3)
Core
Internationalization
Tracking
()
VERIFIED
FIXED
M10
People
(Reporter: ftang, Assigned: rpotts)
References
()
Details
Depend on Necko.
Reporter | ||
Updated•25 years ago
|
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.
Updated•25 years ago
|
Comment 2•25 years ago
|
||
I created the test cases for Http charset in http://babel/tests/http_charset.html
Reporter | ||
Updated•25 years ago
|
Assignee: ftang → warren
Status: ASSIGNED → NEW
Target Milestone: M9 → M8
Reporter | ||
Comment 3•25 years ago
|
||
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.
Updated•25 years ago
|
Status: NEW → ASSIGNED
Updated•25 years ago
|
Target Milestone: M8 → M9
Comment 4•25 years ago
|
||
necko now lands in m9
Comment 7•25 years ago
|
||
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!
Updated•25 years ago
|
Severity: normal → blocker
Summary: HTTP charset does not work → [Blocker]HTTP charset does not work
Target Milestone: M9 → M10
Comment 9•25 years ago
|
||
I move this to M10. I put the broker for M10.
Assignee | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 10•25 years ago
|
||
I've added GetCharset() to nsIHTTPChannel...
-- rick
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 11•25 years ago
|
||
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.
Description
•