fix(lib-storage): fix bucket duplication in hostname #4157
Merged
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.
Issue
#4109
Description
endpoints rulesets can resolve with the bucket already prefixed in the hostname, but custom endpoints might not include it. Therefore this PR proposes that we check for the bucket prefix when constructing an upload Location.
This is a best-guess heuristic. If someone has an identical hostname and bucket like hostname
abcd.com
and a bucket ofabcd
, it will not append the bucket name to createabcd.abcd.com/key
. In such cases the user will have to specify a hostname including the bucket name.Testing
added unit tests