@dkocher commented

The bucket name is ommited in the path but instead added to the domain name. E.g. test.s3.amazonaws.com/foo.txt which should resolve correctly.

9ba40d7 commented

Some more possibly relevant information:

• I don't have a path in my S3 connection.

• I use "New Folder..." to make the folder, I called it "Bogus"

• I then dragged a file named Marriott-bed-4.jpg into the folder.

• Right click to Copy URL of a file dragged in there results in https://s3.amazonaws.com/Marriott-bed-4.jpg

It's definitely a bug, just not sure what's different between our two setups. Feel free to contact me over email if you need more information. I'm on the CC.

@dkocher commented

I can confirm this now. It happens if you create a bucket using an uppercase character. Because the DNS system is not case sensitive, uppercase buckets are not accessible using a virtual hostname for the bucket name.

@dkocher commented

In 0cd84f2.