You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of the ResponseEntityResultHandler only writes each ResponseEntity response header on the response only if there's none already for that header name.
This behavior is not consistent with what's being done in Spring MVC with the HttpEntityMethodProcessor - it also creates issues for some use cases (see reference URL for an example).
Brian Clozel opened SPR-17082 and commented
The current implementation of the
ResponseEntityResultHandler
only writes eachResponseEntity
response header on the response only if there's none already for that header name.This behavior is not consistent with what's being done in Spring MVC with the
HttpEntityMethodProcessor
- it also creates issues for some use cases (see reference URL for an example).Given the following code snippet:
In such a case, here's what happens:
Affects: 5.0.7
Reference URL: spring-projects/spring-boot#13635
Issue Links:
Referenced from: commits 195f3f0, 407bd96
The text was updated successfully, but these errors were encountered: