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
Currently, the response encoding is determined from the charset attribute of the content-type response header. If it's missing or isn't recognized, it falls back to LATIN-1 according to RFC 2616. Although the server should always provide an accurate charset attribute, it may be useful to allow the encoding to be explicitly overridden in cases where the requester does not have control of the server.
The text was updated successfully, but these errors were encountered:
Currently, the response encoding is determined from the
charset
attribute of thecontent-type
response header. If it's missing or isn't recognized, it falls back to LATIN-1 according to RFC 2616. Although the server should always provide an accuratecharset
attribute, it may be useful to allow the encoding to be explicitly overridden in cases where the requester does not have control of the server.The text was updated successfully, but these errors were encountered: