You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2020/06/23 18:37:00 UTC

[jira] [Comment Edited] (MRESOLVER-128) Support smart checksums for Wagon Transporter

    [ https://issues.apache.org/jira/browse/MRESOLVER-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143207#comment-17143207 ] 

Michael Osipov edited comment on MRESOLVER-128 at 6/23/20, 6:36 PM:
--------------------------------------------------------------------

Correct, I see no way to support this cross Wagon providers. Do we want to retain this issue anyway? Another issue is that ETags are opaque and are not subject to interpretation. I consider the approach taken by Nexus invalid and breaking RFC 7234. A custom header would have been better.


was (Author: michael-o):
Correct, I see no way to support this cross Wagon providers. Do we want to retain this issue anyway?

> Support smart checksums for Wagon Transporter
> ---------------------------------------------
>
>                 Key: MRESOLVER-128
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-128
>             Project: Maven Resolver
>          Issue Type: Improvement
>          Components: resolver
>            Reporter: Konrad Windszus
>            Priority: Major
>
> The HTTP transporter can use checksum implicitly transferred via the {{ETag}} response header: https://github.com/apache/maven-resolver/blob/47edcfe69c4e52ced4cb93d65b7348b5645cdd68/maven-resolver-transport-http/src/main/java/org/eclipse/aether/transport/http/HttpTransporter.java#L526. This feature is called smart checksums.
> The same functionality should also be supported in Wagon.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)