You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Historically, HTTP has allowed field content with text in the ISO-8859-1 charset, supporting other charsets only through use of RFC2047 encoding. In practice, most HTTP header field values use only a subset of the US-ASCII charset. Newly defined header fields SHOULD limit their field values to US-ASCII octets. A recipient SHOULD treat other octets in field content (obs-text) as opaque data.
The text was updated successfully, but these errors were encountered:
If a server returns a non-ASCII character in a header, the curl client should still handle the response, but it raises an UnicodeDecodeError instead.
Code:
Got:
RFC 7230 says:
The text was updated successfully, but these errors were encountered: