Improve API for constructing HTTP error responses #281
+84
−54
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SentryMan
approved these changes
Aug 17, 2025
rbygrave
approved these changes
Aug 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a simple extension to
HttpResponseException.Unlike Javalin, which has e.g.
UnauthorizedResponse, we do not have such exceptions for every HTTP error code response.Furthermore, for the ones we do have them for, e.g. Javalin's
BadRequestResponsewe haveBadRequestException, you still need to provide a message.With this PR, you can now run
throw new HttpResponseException(UNAUTHORIZED_401)which will use the messageUnauthorizedlike Javalin doesthrow new HttpResponseException(UNAUTHORIZED_401, "Unauthorized [forgot to mash the potatoes!])for a custom message.