[
https://issues.apache.org/jira/browse/MRESOLVER-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MRESOLVER-600:
------------------------------------
Description:
HTTP1.1 [RFC 9112 -
HTTP/1.1|https://www.rfc-editor.org/rfc/rfc9112.html#name-status-line] section
4 defines the response status code to optionally include a text description
(human readable) of the reason for the status code.
There is an additional [RFC9457 - Problem Details for HTTP
APIs|https://www.rfc-editor.org/rfc/rfc9457] which makes use of the body to
inform of a reason for the error response allowing for easier investigation.
h2. Why is this important
[RFC9113|https://www.rfc-editor.org/rfc/rfc9113] is the HTTP2 protocol standard
and the response status only considers the [status
code|https://www.rfc-editor.org/rfc/rfc9113#name-response-pseudo-header-fiel]
and not the reason phrase, as such important information can be lost in helping
the client determine a route cause of a failure.
was:
HTTP1.1 [RFC 9112 -
HTTP/1.1|https://www.rfc-editor.org/rfc/rfc9112.html#name-status-line] section
4 defines the response status code to optionally include a text description
(human readable) of the reason for the status code.
There is an additional [RFC9457|https://www.rfc-editor.org/rfc/rfc9457] which
makes use of the body to inform of a reason for the error response allowing for
easier investigation.
h2. Why is this important
[RFC9113|https://www.rfc-editor.org/rfc/rfc9113] is the HTTP2 protocol standard
and the response status only considers the [status
code|https://www.rfc-editor.org/rfc/rfc9113#name-response-pseudo-header-fiel]
and not the reason phrase, as such important information can be lost in helping
the client determine a route cause of a failure.
> Implement RFC 9457 - Problem Details for HTTP APIs
> --------------------------------------------------
>
> Key: MRESOLVER-600
> URL: https://issues.apache.org/jira/browse/MRESOLVER-600
> Project: Maven Resolver
> Issue Type: New Feature
> Components: Resolver
> Reporter: Mark Dodgson
> Assignee: Tamas Cservenak
> Priority: Minor
> Fix For: 2.0.2
>
>
> HTTP1.1 [RFC 9112 -
> HTTP/1.1|https://www.rfc-editor.org/rfc/rfc9112.html#name-status-line]
> section 4 defines the response status code to optionally include a text
> description (human readable) of the reason for the status code.
> There is an additional [RFC9457 - Problem Details for HTTP
> APIs|https://www.rfc-editor.org/rfc/rfc9457] which makes use of the body to
> inform of a reason for the error response allowing for easier investigation.
> h2. Why is this important
> [RFC9113|https://www.rfc-editor.org/rfc/rfc9113] is the HTTP2 protocol
> standard and the response status only considers the [status
> code|https://www.rfc-editor.org/rfc/rfc9113#name-response-pseudo-header-fiel]
> and not the reason phrase, as such important information can be lost in
> helping the client determine a route cause of a failure.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
