What I can dig up today is that back in 2011, they documented that bucket names cannot look like IPv4 addresses and the character set was a-z0-9.-, but they fai

What I can dig up today is that back in 2011, they documented that bucket names cannot look like IPv4 addresses and the character set was a-z0-9.-, but they failed to prevent 192.168.5.123 or _foo. I recall there were more edge cases around HTTP headers, but they don't seem to have been recorded as test cases -- it's been too long for me to remember details, I may have simply ran out of time / real world interop got good enough to prioritize something else. 2011 state, search for fails_on_aws: https://github.com/tv42/s3-tests/blob/master/s3tests/functional/test_s3.py https://github.com/tv42/s3-tests/blob/master/s3tests/functio... Current state, I can't speak to the exact semantics of the annotations today, they could simply be annotating non-AWS features: https://github.com/ceph/s3-tests/blob/master/s3tests/functional/test_s3.py https://github.com/ceph/s3-tests/blob/master/s3tests/functio...