jclouds/jclouds — pull request #684 by whitlockjc (2012-06-21 23:09:45+00:00)
Title: Issue 992: Fix AWS S3 to work with non-DNS, but still valid, named buckets.

Prior to this commit, jclouds wouldn't allow you to interact with any buckets
in S3 that were named with uppercase characters. Per AWS S3 docs, this
non-standard naming is valid in US regions only. This update fixes jclouds so
that it can interact with, and even attempt to create, buckets with uppercase
characters for AWS S3 without actually impacting other S3 implementations. This
fix also will not have any impact in non-US regions other than instead of a
bucket name validation error you'll get an InvalidBucketName error back from
AWS S3 when you attempt to create a bucket with an uppercase character in a
non-US region. To summarize, nothing changes other than US regions now allow
creation of bucket names with upper case characters and jclouds now can
interact with these non-standard named buckets without failure.