spring-projects / spring-projects/spring-boot
More helpful 404 error page
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
This is just a suggestion for enhancing the default 404 error pages.
Other web frameworks (for example Django) show detailed information about how it attempted to resolve the request path, i.e. which local or "classpath" paths were checked.
Therefore, it would be nice if Spring Boot's default 404 error page would not just display the "not found" error, but also how the full paths (based on the configured resource locations) look like that could not be resolved.
Of course this would only be advisable in "debug" mode / during development. Not sure how one would determine that in Spring Boot, since there is no simple "DEBUG" variable like in Django and I don't know of any standard profile names for development / production environments.
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
The issue names no files, tests, or entry points. Start by locating Spring Boot's default 404 error-page handling and how configured resource locations are resolved, then determine how development or debug mode should be identified. Done means agreeing on the scope and safely showing unresolved paths only in the intended development context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100