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
Hi! We've met a problem to display cyrillic letters - because response didn't contain correct charset in header, User-agent chose the best default option. Google Chrome, for example, thaught that utf-8 text was encoded in win-1251.
What about making options are more flexible with Charset Encodind as a parameter?
{
q.ResponseEncoding= Encoding.UTF8;
});```
The text was updated successfully, but these errors were encountered:
Hi! We've met a problem to display cyrillic letters - because response didn't contain correct charset in header, User-agent chose the best default option. Google Chrome, for example, thaught that utf-8 text was encoded in win-1251.
What about making options are more flexible with Charset Encodind as a parameter?
The text was updated successfully, but these errors were encountered: