Repository navigation
Cache Maven checksums and signatures as artifacts - #484
Merged
Merged
Conversation
Checksum and .asc files beside a versioned artifact are as immutable as the artifact, but were routed through the metadata path: uncached until a first successful fetch, with no retry or circuit breaker. A build pulling hundreds of artifacts sent as many checksum requests straight to Maven Central, which rate-limited the proxy, after which every further checksum request still went upstream and failed. Only maven-metadata.xml and its own checksums stay on the metadata path, since the version listing changes with each release.
andrew
approved these changes
Oct 15, 2026
andrew
left a comment
andrew
left a comment
Contributor
There was a problem hiding this comment.
Thanks. Keeping only maven-metadata.xml and its sidecars on the metadata path is the right split, and caching checksums alongside their artifact also stops a cached non-unique snapshot jar disagreeing with a freshly fetched checksum.
This was referenced Oct 15, 2026
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Maven handler sends checksum (
.sha1,.md5,.sha256,.sha512) and.ascfiles that sit beside a versioned artifact through the metadata path. They aren't cached until a first successful fetch, and that path has no retry or circuit breaker. A build that pulls hundreds of artifacts sends as many checksum requests straight to Maven Central. Central then rate-limits the proxy, and every later checksum request still goes upstream and fails.These files are as immutable as the artifact they sit beside, so this caches them as artifacts. Only
maven-metadata.xmland its own checksums stay on the metadata path, because the version listing changes with each release.Tested with
go build ./...,go vet ./...andgo test ./..., and by running the proxy against a live server.