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

CharacterEncodingFilter should have an option to avoid forcing encoding on responses [SPR-14240] #18813

Closed
spring-issuemaster opened this issue May 3, 2016 · 0 comments
Assignees
Milestone

Comments

@spring-issuemaster
Copy link
Collaborator

@spring-issuemaster spring-issuemaster commented May 3, 2016

Brian Clozel opened SPR-14240 and commented

Setting the forceEncoding option on this filter not only forces the encoding on the request, but also on the response itself, which is rather agressive and can lead to issues like described in #18698.

Adding a new setForceResponseEncoding option should allow to selectively force the encoding on the request only. Of course, this option should be set to true by default for backwards compatibility.


Referenced from: commits 05b29a4, 76ee468

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.