Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
StringHttpMessageConverter should assume charset UTF-8 for application/json [SPR-17568] #22100
When using "
So the suggestion would be to add an exception in the StringHttpMessageConverter to use UTF-8 charset for application/json.
Referenced from: commits 05d6162
Thomas Meyer commented
When using Jersey as client it's especially problematic as Jersey's StringMessageProvider (https://github.com/jersey/jersey/blob/master/core-common/src/main/java/org/glassfish/jersey/message/internal/StringMessageProvider.java ) uses default encoding UTF-8 for content-type application/json.
Rossen Stoyanchev commented
This is also supported by the current HTTP 1.1 spec RFC 7231:
We can update