HttpMessageConverter selection as a result of @ResponseBody should consider the requested content type [SPR-5923] #10592
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
type: enhancement
A general enhancement
Milestone
Rossen Stoyanchev opened SPR-5923 and commented
Currently when a method is annotated with
@ResponseBody
, the AnnotationMethodHandlerAdapter loops over a list of registered HttpMessageConverters and asks each one if it supports the type of the returned value. In order to support alternating between different content types for the same resource, the AnnotationMethodHandler should take into consideration the content type requested by the client and try to find a message converter that supports both the type of the returned value as well as the client requested content type.Affects: 3.0 M4
Referenced from: commits b11970e
The text was updated successfully, but these errors were encountered: