s3 virtual host access resolution inconsistent

[MilesTails]

Hi,

I've read through the release notes and can see that in v1 it states: Virtual host style bucket name resolving is enabled by default for S3 and GCSS. However this doesn't seem to be the case.

I've created a new bucket miles-bucket-us-east-1

s3://miles-bucket-us-east-1/ would translate to https://miles-test-us-east-1.s3.amazonaws.com however from my network traffic logs I can see that the traffic defaults to https://s3.amazonaws.com/miles-bucket-us-east-1

Command to replicate:

s5cmd ls s3://miles-bucket-us-east-1/

I can't see any options that I need to specify to force the s5cmd to use virtual host. Am I doing something wrong?

[MilesTails]

On further investigation this appears it could be something to do with region detection, is there a way to skip or pass a parameter to avoid region detection?

Presumably related to: aws/aws-sdk-go#3115