[ https://issues.apache.org/jira/browse/MRESOLVER-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880925#comment-17880925 ]
ASF GitHub Bot commented on MRESOLVER-600: ------------------------------------------ doddi commented on code in PR #576: URL: https://github.com/apache/maven-resolver/pull/576#discussion_r1753934784 ########## pom.xml: ########## @@ -289,6 +289,12 @@ <artifactId>jimfs</artifactId> <version>1.3.0</version> </dependency> + + <dependency> + <groupId>com.google.code.gson</groupId> + <artifactId>gson</artifactId> + <version>2.10.1</version> Review Comment: https://github.com/apache/maven-resolver/pull/576/commits/1c7138e6471a81fdc67a9510e26d1e42d9205f27 > 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)