Is HTTP headers limited to US-ASCII charset?
Can I use unicode characters in HTTP headers?
Edit:
I want to do like this:
WebClient myWebClient = new WebClient();
myWebClient.Headers.Add("Content-Type","یونیکد");
-
is that what you're looking for? >> w3.org/International/O-HTTP-charsetJMax– JMax2011-09-27 09:51:33 +00:00Commented Sep 27, 2011 at 9:51
-
possible duplicate of Which encoding is used by the HTTP protocol?Thilo– Thilo2011-09-27 09:55:03 +00:00Commented Sep 27, 2011 at 9:55
-
Since that Content-Type does not match any of the official MIME-Types, no standard software can use it. What is the effect you intend to achieve?foo– foo2019-06-27 16:00:12 +00:00Commented Jun 27, 2019 at 16:00
Add a comment
|
2 Answers
First of all, the header field in your example does not allow what you want; media type names are ASCII.
In theory, HTTP header field values can transport anything; the tricky part is to get all parties (sender, receiver, and intermediates) to agree on the encoding.
Thus, the safe way to do this is to stick to ASCII, and choose an encoding on top of that, such as the one defined in RFC 5987.
2 Comments
Piotr Dobrogost
It would be very useful to know which popular User Agents and proxies support RFC 5987.
Julian Reschke
Piotr: RFC 5987 can only be used for parameters in header fields, and then only if sender and receivers agree on it, such as in Content-Disposition's filename parameter.
Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
1 Comment
mmmmmm
Dosn't this apply to the document not the headers?
