MappingJackson2HttpMessageConverter might be too specific in its Charset support #25322
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
status: backported
An issue that has been backported to maintenance branches
status: duplicate
A duplicate of another issue
status: feedback-provided
Feedback has been provided
type: regression
A bug that is also a regression
Milestone
With this eb0aae0#diff-ea14ba194c2adb7f8aa7f97a2ca5bcc7, spring web Jackson2 Converter introduced an enum set limiting UTF options. In a testing scenario we use "US-ASCII" which was working until now. Since 5.2.7, the controller will rejects requests, failing to decode.
Is that the intended behavior or should
ENCODINGS
map include US-ASCII as well ?The text was updated successfully, but these errors were encountered: