s3cmd falls back to sigv2 when underscore is in bucket name
When using s3cmd to upload to a bucket where the name has an underscore in it, it falls back to signature_v2, and when the bucket has no underscore it uses signature_v4. I dont think buckets with underscores and capitals need to be changed or not used, its just that new buckets can not be created with those in the names. I have tested this on the latest version (2.0.2). I see under 2.0.1 a fix for upper-case: Fixed signature issues due to upper-case in hostname I wonder if fixing the underscore was...