michael-o commented on a change in pull request #140:
URL: https://github.com/apache/maven-resolver/pull/140#discussion_r771609179
##########
File path: src/site/markdown/smart-checksum-strategies.md
##########
@@ -39,12 +39,15 @@ way. Naturally, this means only SHA-1 is available in
artifact response header.
Emitted by: Sonatype Nexus2 only.
-## Non-standard headers
+## Non-standard `X-` headers
-Some MRMs and Maven Central emit headers `x-checksum-sha1` and
`x-checksum-md5`. Resolver
-will detect these and use their value.
+Maven Central emit headers `x-checksum-sha1` and `x-checksum-md5` along with
artifact response.
+Google GCS on the other hand uses `x-goog-meta-checksum-sha1` and
`x-goog-meta-checksum-md5` heaers.
+Resolver will detect these and use their value.
-Emitted by: Maven Central and Artifactory, maybe by some others as well.
+Emitted by: Maven Central and some MRMs and . Kinda , maybe by some others as
well.
Review comment:
This sentence is weird
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
