Before this commit, AbstractJackson2HttpMessageConverter and subclasses
did not check media type encoding in the canRead and canWrite
methods. As a result, the converter reported that it can write
(for instance) "application/json;charset=ISO-8859-1", but in practice
wrote the default charset (UTF-8).
This commit fixes that bug.
See: gh-25076
@ -167,6 +173,14 @@ public abstract class AbstractJackson2HttpMessageConverter extends AbstractGener
@@ -167,6 +173,14 @@ public abstract class AbstractJackson2HttpMessageConverter extends AbstractGener
@ -180,6 +194,14 @@ public abstract class AbstractJackson2HttpMessageConverter extends AbstractGener
@@ -180,6 +194,14 @@ public abstract class AbstractJackson2HttpMessageConverter extends AbstractGener
@ -211,6 +233,14 @@ public abstract class AbstractJackson2HttpMessageConverter extends AbstractGener
@@ -211,6 +233,14 @@ public abstract class AbstractJackson2HttpMessageConverter extends AbstractGener
@ -333,10 +363,9 @@ public abstract class AbstractJackson2HttpMessageConverter extends AbstractGener
@@ -333,10 +363,9 @@ public abstract class AbstractJackson2HttpMessageConverter extends AbstractGener
@ -359,4 +388,9 @@ public abstract class AbstractJackson2HttpMessageConverter extends AbstractGener
@@ -359,4 +388,9 @@ public abstract class AbstractJackson2HttpMessageConverter extends AbstractGener
@ -45,6 +46,8 @@ public class MappingJackson2SmileHttpMessageConverterTests {
@@ -45,6 +46,8 @@ public class MappingJackson2SmileHttpMessageConverterTests {
@ -52,6 +55,8 @@ public class MappingJackson2SmileHttpMessageConverterTests {
@@ -52,6 +55,8 @@ public class MappingJackson2SmileHttpMessageConverterTests {
@ -50,6 +50,8 @@ public class MappingJackson2XmlHttpMessageConverterTests {
@@ -50,6 +50,8 @@ public class MappingJackson2XmlHttpMessageConverterTests {
@ -57,6 +59,8 @@ public class MappingJackson2XmlHttpMessageConverterTests {
@@ -57,6 +59,8 @@ public class MappingJackson2XmlHttpMessageConverterTests {