Skip to content

api: Allow *.amazonaws.com but not s3 endpoints#729

Merged
vadmeste merged 1 commit into
minio:masterfrom
vadmeste:mc/issue/2198
Jul 2, 2017
Merged

api: Allow *.amazonaws.com but not s3 endpoints#729
vadmeste merged 1 commit into
minio:masterfrom
vadmeste:mc/issue/2198

Conversation

@vadmeste
Copy link
Copy Markdown
Member

New() was rejecting endpoints with this address format: *.amazonaws.com,
however, it should only reject *.s3.amazonaws.com. With this PR,
addresses such as foo.us-east-1.elb.amazonaws.com will be accepted.

Fixes minio/mc#2198

New() was rejecting enpoints with this address format: *.amazonaws.com,
however, it should only reject *.s3.amazonaws.com. With this PR,
addresses such as foo.us-east-1.elb.amazonaws.com will be accepted.
@vadmeste
Copy link
Copy Markdown
Member Author

I didn't see the test error here. Now it is fixed. Can you review @harshavardhana and @balamurugana ?

Comment thread utils.go
return ErrInvalidArgument("Endpoint url cannot have fully qualified paths.")
}
if strings.Contains(endpointURL.Host, ".amazonaws.com") {
if strings.Contains(endpointURL.Host, ".s3.amazonaws.com") {
Copy link
Copy Markdown
Member

@harshavardhana harshavardhana Jun 30, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how does this work for s3.amazonaws.com ?

@deekoder deekoder requested review from balamurugana and donatello and removed request for balamurugana and donatello June 30, 2017 18:03
Copy link
Copy Markdown
Member

@balamurugana balamurugana left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not Tested

@vadmeste vadmeste merged commit 2263a34 into minio:master Jul 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants