spring-projects / spring-projects/spring-boot

Support 'server.error.include-*' functionality when 'spring.mvc.problemdetails.enabled' is active

Open
#33,944 2 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: enhancement
Dominant language
Java
Stars
81.5k
Forks
42.7k
Avg merge
2d 4h
Merged PRs (30d)
65

Description

If we add support for the RFC 7807 Problem Details spec by including the spring.mvc.problemdetails.enabled=true property, then the server.error.include-* (e.g. server.error.include-binding-errors=always and server.error.include-message=always) properties are ignored, the response doesn't retrieve the relevant data.

IMO it would be suitable to allow mixing these two features to obtain an application/problem+json response with all the error information we want.

Note: this issue I submitted to the Spring Core project is somewhat related:
https://github.com/spring-projects/spring-framework/issues/29849

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the interaction between spring.mvc.problemdetails.enabled and the server.error.include-* properties, especially server.error.include-binding-errors and server.error.include-message. Read the related Spring Framework issue and the existing Spring Boot Problem Details handling. Done means an application/problem+json response includes the configured error information when those properties are enabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring-boot
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.