Enhance Status.java with Additional Standard HTTP Status Codes #8444
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.
Resolves #8443
This PR extends the
Status.java
class within Helidon to include a series of standard HTTP status codes that were previously absent. These additions aim to align Helidon with web standards, facilitating developers to utilize a broader spectrum of HTTP responses directly within their applications, especially for those leveraging WebDAV or requiring precise network error management.Newly Added Status Codes:
Key Enhancements:
@since
annotation to4.0.6
for all newly added status codes, marking their introduction in this version.Targeted Environment:
Motivation:
The inclusion of these status codes fills existing gaps in Helidon's HTTP status code support, offering developers a more versatile toolkit for HTTP response management. This enhancement is essential for ensuring that applications can handle a wider range of web protocols and standards, particularly benefiting those that integrate with WebDAV or require specific network authentication handling.
Impact:
This contribution introduces no breaking changes. Instead, it broadens Helidon's adherence to established web standards and enriches the developer's toolkit for handling diverse HTTP scenarios out of the box.