Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

S3 fails verification checks when a bucket name contains upper-case characters #4

Closed
leejo opened this issue Apr 5, 2016 · 1 comment
Closed

S3 fails verification checks when a bucket name contains upper-case characters #4

leejo opened this issue Apr 5, 2016 · 1 comment

Comments

@leejo
Copy link
Owner

leejo commented Apr 5, 2016

One workaround is to use "s3.amazonaws.com/Bucket-Name" instead of "Bucket-Name.s3.amazonaws.com" in the URL
@leejo
Copy link
Owner Author

leejo commented Apr 7, 2016

As per AWS Bucket Restrictions - "Rules for Bucket Naming":

Bucket names can contain lowercase letters, numbers, and hyphens.

This is a restriction on the AWS side, not a bug in the module and exists because:

We recommend that all bucket names comply with DNS naming conventions. These conventions are enforced in all regions except for the US East (N. Virginia) region.

@leejo leejo closed this as completed Apr 7, 2016
leejo added a commit that referenced this issue Apr 7, 2016
@leejo
resolve #4, resolve #5 - DNS bucket check / URI escaping
f0fc7b5 
be a bit smarter in the _is_dns_bucket check (actually do checking)
to make sure a none valid DNS bucket name isn't marked as valid so
the bucket is used in the path rather than the hostname

make sure to uri_escape files in paths to avoid infinite loops due
to spaces in filenames

bump VERSION and Changes for CPAN release
leejo added a commit that referenced this issue Apr 7, 2016
@leejo
resolve #4, resolve #5 - DNS bucket check / URI escaping
10bb998 
be a bit smarter in the _is_dns_bucket check (actually do checking)
to make sure a none valid DNS bucket name isn't marked as valid so
the bucket is used in the path rather than the hostname

make sure to uri_escape files in paths to avoid infinite loops due
to spaces in filenames

bump VERSION and Changes for CPAN release
leejo added a commit that referenced this issue Apr 7, 2016
@leejo
resolve #4, resolve #5 - DNS bucket check / URI escaping
bf4c994 
be a bit smarter in the _is_dns_bucket check (actually do checking)
to make sure a none valid DNS bucket name isn't marked as valid so
the bucket is used in the path rather than the hostname

make sure to uri_escape files in paths to avoid infinite loops due
to spaces in filenames

bump VERSION and Changes for CPAN release
leejo added a commit that referenced this issue Apr 8, 2016
@leejo
ref #4, ref #5, fix more DNS bucket endpoints
ef7f548 
couple more places we need to check if the bucket is a valid DNS
bucket and DTRT if it is not, also another places to uri_escape
the params

it seems this code is poorly factored and has some repetition that
code be refactored out, but at the moment i'm not inclined to fix
leejo added a commit that referenced this issue Apr 8, 2016
@leejo
ref #4, ref #5, fix more DNS bucket endpoints
9cb7967 
couple more places we need to check if the bucket is a valid DNS
bucket and DTRT if it is not, also another places to uri_escape
the params

it seems this code is poorly factored and has some repetition that
code be refactored out, but at the moment i'm not inclined to fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@leejo