Open
Bug 1765290
Opened 3 years ago
Updated 2 years ago
Figure out UTF8/UTF16 handling in early hint code
Categories
(Core :: Networking: HTTP, task, P3)
Core
Networking: HTTP
Tracking
()
NEW
People
(Reporter: manuel, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Currently early hints receive the link header as utf8 encoded string. This makes sense, because http headers are ASCII-encoded. Parsing the header string and using the header values require UTF16 however. It would be good if we could use just utf8-functions there.
https://phabricator.services.mozilla.com/D137885#inline-793476
Updated•3 years ago
|
Severity: -- → S3
Priority: -- → P2
Whiteboard: [necko-triaged]
Reporter | ||
Comment 1•2 years ago
•
|
||
Reporter | ||
Comment 2•2 years ago
•
|
||
It seems to me like the way forward is to change the encoding from utf16 to utf8 in the LinkHeader and all functions working with LinkHeader attributes (s/nsString/nsCString):
struct LinkHeader {
nsString mHref;
nsString mRel;
nsString mTitle;
nsString mIntegrity;
nsString mSrcset;
nsString mSizes;
nsString mType;
nsString mMedia;
nsString mAnchor;
nsString mCrossOrigin;
nsString mReferrerPolicy;
nsString mAs;
...
};
Updated•2 years ago
|
Priority: P2 → P3
Updated•2 years ago
|
Severity: S3 → N/A
You need to log in
before you can comment on or make changes to this bug.
Description
•