[
https://issues.apache.org/jira/browse/MRESOLVER-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880690#comment-17880690
]
ASF GitHub Bot commented on MRESOLVER-600:
------------------------------------------
hboutemy commented on PR #576:
URL: https://github.com/apache/maven-resolver/pull/576#issuecomment-2341244372
ok, IIUC, the exception gets translated into a Maven CLI message without
changing Maven core code: nice
I don't know if we have an IT to check that...
> Implement RFC 9457
> ------------------
>
> Key: MRESOLVER-600
> URL: https://issues.apache.org/jira/browse/MRESOLVER-600
> Project: Maven Resolver
> Issue Type: New Feature
> Components: Resolver
> Reporter: Mark Dodgson
> Priority: Minor
>
> HTTP1.1 [RFC
> 9112|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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
