spring-projects / spring-projects/spring-boot
Write HTTP response headers contributed by exceptions in WebFlux error handling
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
As of spring-projects/spring-framework#23741, Spring Framework allows ResponseStatusException instances to contribute HTTP headers to the error response.
The current infrastructure with AbstractErrorWebExceptionHandler and DefaultErrorWebExceptionHandler allow for user extension but is causing some challenges:
- it duplicates efforts with what's being done in Spring Framework, as it needs to handle error responses completely
- it doesn't allow to easily let exceptions contribute to the actual response.
This issue is about catching up with spring-projects/spring-framework#23741, and also checking whether there is a way to improve the situation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading AbstractErrorWebExceptionHandler and DefaultErrorWebExceptionHandler, then compare their handling with Spring Framework issue #23741. Trace how ResponseStatusException headers reach the response and determine what behavior should change or be removed. Done means exception-contributed HTTP headers are preserved without duplicating Spring Framework's handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100