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
I have the same issue when the Content-type header is set to 'application/json' and has no charset appended (according to RFC 4627 there should be no charset anyway.) Safari's text encoding of 'default' causes this; changing to UTF-8 fixes it. Is this an issue with Safari or should the extension be choosing UTF-8 as the default charset?
German or russian umlauts are not displayed properly (displayed as escape characters)
The text was updated successfully, but these errors were encountered: