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
When using WebFlux, server.error.include-binding-errors=ALWAYS no longer has an effect when the BindingResult exception is the cause of a ResponseStatusException
#41984
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
This is problematic if the cause was an instance of BindingResult as this is no longer true, so the errors aren't added regardless of property value....
I can fix this by exposing a custom ErrorAttributes Bean in each app. However, is this the intention or is this a bug? If it's the former then a documentation update would be handy as this is a breaking change.
The text was updated successfully, but these errors were encountered:
wilkinsona
changed the title
server.error.include-binding-errors=ALWAYS ignored in Boot 3.2.6+
When using WebFlux, server.error.include-binding-errors=ALWAYS is ignored
Aug 21, 2024
wilkinsona
changed the title
When using WebFlux, server.error.include-binding-errors=ALWAYS is ignored
When using WebFlux, server.error.include-binding-errors=ALWAYS has no effect when the BindingResult exception is the cause of a ResponseStatusException
Aug 21, 2024
wilkinsona
changed the title
When using WebFlux, server.error.include-binding-errors=ALWAYS has no effect when the BindingResult exception is the cause of a ResponseStatusException
When using WebFlux, server.error.include-binding-errors=ALWAYS no longer has an effect when the BindingResult exception is the cause of a ResponseStatusException
Aug 21, 2024
Background
Since Boot 2.3 binding errors are no longer included in the default error page by default.
The resolution, until this commit, was to set this property accordingly.
server.error.include-binding-errors=ALWAYS
Unfortunately this no longer works in Boot 3.2.6+.
Expected Behaviour/Repro
Full repro here
Code
When we hit http://localhost:8080/manualBindError
Expected
Something resembling the below - with errors intact.
Actual
Errors are missing.
Root Cause
The code below was removed from
DefaultErrorAttributes
.This is problematic if the cause was an instance of
BindingResult
as this is no longer true, so the errors aren't added regardless of property value....Resolution?
I can fix this by exposing a custom
ErrorAttributes
Bean in each app. However, is this the intention or is this a bug? If it's the former then a documentation update would be handy as this is a breaking change.The text was updated successfully, but these errors were encountered: