Repository navigation
Support R2 URLs with jurisdictions - #815
Merged
Merged
Conversation
Contributor
Author
|
The CI fail appears unrelated to the changes here |
alamb
approved these changes
Aug 17, 2026
alamb
left a comment
alamb
left a comment
Contributor
There was a problem hiding this comment.
Looks good to me -- thank you @Kharacternyk
3 of 5 tasks
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.
Which issue does this PR close?
Closes #814.
Rationale for this change
Jurisdiction-restricted buckets on R2 are only accessible through special URLs, which are not currently accepted by the parser. Currently there are only two jurisdictions,
euandfedramp, but there may be more in the future, so I've kept the pattern general.What changes are included in this PR?
Extended the URL parser.
Are there any user-facing changes?
Yes, valid R2 URLs for jurisdiction-restricted buckets no longer fail to be parsed. I've updated the relevant doc comment.