Repository navigation
Conversation
The S3 door now reports its transfers with the protocol name S3 (version 1.1) instead of Http. Note this for site administrators on the S3 page and for PoolManager protocol units. Assisted-by: DeepSeek-V4.1-Flash/DeepSeek AI
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
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.
Suggested documentation update for 9bd02ec ("s3: enforce S3 as protocol name"). AI-generated — please review for accuracy before merging.
The commit makes the S3 door report its transfers with the protocol name
S3(version 1.1) rather thanHttp, and registers theS3-1transfer service in the pool. The docs now note this on the S3 door page and in the PoolManager protocol-unit description, so site administrators know that billing entries showS3-1.1and PoolManager protocol units and stage-protection patterns matchS3/1.