Option to use path style for bucket endpoint (instead of DNS)

[toehio]

This is especially useful when using a custom S3 endpoint. This comment says it all:
"Instead of using the DNS name of the bucket (e.g. BUCKET.s3.amazonaws.com) use the path style (e.g. s3.amazonaws.com/BUCKET/)".

This can be enabled when initializing the S3 object, or through the setter.

[kmichailg]

I think we need this. For (local) development and testing, I use https://github.com/jamhall/s3rver. Unfortunately, using the dns to access a bucket is quite troublesome as it is not set up automatically. I would have to add another proxy/reverse proxy in apache for it to work. So, I second this @tpyo 👍

[kmichailg]

Hi @tpyo, any updates on this? This is a much appreciated change. I've been using this fork for quite some time now. Didn't have any issues so far. Is there any security issue that I should be aware?

[alexstine]

@toehio Would this PR fix an error like this?

[02-Oct-2017 14:22:55 UTC] PHP Warning: S3::getBucket(): [PermanentRedirect] The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint. in /wp-content/plugins/cloud-backups/classes/aws/s3.php on line 437

I need to access AWS with "bucket.s3.us-east-2.amazonaws.com" to get rid of this error I think. Would be nice to have this fixed so I can use whatever region instead of us-east-1 where /bucket/path/file.ext is still supported.

Thanks.

[toehio]

@tech55541 yes, I think this PR should fix that.

[kmichailg]

Hi @tpyo, long time user of this package. Recently returned here to find myself facing the same problem of using bucket endpoints instead of dns endpoints. Is there any problem with the solution proposed? I've abandoned using this fork since the master had updates I needed on a production build. Would be happy to help testing this.