René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"AbstractJackson2HttpMessageConverter - Check for encoding breaks JSON to POJO de-serialization experience","articleBody":"**Affects:** 5.2.7 (Spring Boot 2.3.1)\r\n---\r\nDue to a fix in [Issue #25076](https://github.com/spring-projects/spring-framework/issues/25076)\r\nthe AbstractJackson2HttpMessageConverter also blocks the out-of-the-box JSON to POJO de-serialization for responses with an encoding/character set not being unicode.\r\n\r\nIn our case a GET request to `https://appleid.apple.com/auth/keys` responses with a \r\n`Content-Type: application/json;charset=ISO-8859-1`, which results now in\r\n`org.springframework.web.client.UnknownContentTypeException: Could not extract response: no suitable HttpMessageConverter found for response type [class x.y.z.AppleKeyRequest] and content type [application/json;charset=ISO-8859-1]`.\r\n\r\nIt would be nice to have an option to include non compliant JSON encodings for the given default converters or to have the encoding check as opt-in to be on par with previous default behavior.","author":{"url":"https://github.com/kruegsch","@type":"Person","name":"kruegsch"},"datePublished":"2020-06-12T12:50:54.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":9},"url":"https://github.com/25247/spring-framework/issues/25247"}