Should warn to use HTTP for bucket names with periods. [was: Hostname/IP doesn't match certificate's altnames]

[rcs]

I have a bucket with periods in it, and node's TLS module isn't happy with it.

http://docs.amazonwebservices.com/AmazonS3/latest/dev/VirtualHosting.html

As mentioned in the doc referenced above:

When using virtual hosted-style buckets with SSL, the SSL wild card certificate only matches buckets that do not contain periods. To work around this, use HTTP or write your own certificate verification logic.

Knox could deal with this by using s3/BUCKET style URLs.

[domenic]

Sorry, Knox explicitly doesn't support using the path-style access. See #44 (comment) for some more details on this.

I'll leave this open so we can give a more informative error message when such bucket names are passed in, saying that you should use secure: false.