Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Response encoding #16

Closed
BruTyler opened this issue May 24, 2021 · 1 comment
Closed

Response encoding #16

BruTyler opened this issue May 24, 2021 · 1 comment
Assignees

Comments

@BruTyler
Copy link

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;
 });```

@phnx47
Copy link
Member

phnx47 commented May 25, 2021

Published: v4.4.0

@phnx47 phnx47 closed this as completed May 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants