Re:Amazon S3 will no longer support path-style API requests
by geofft on Friday May 03, 2019 @05:28PM
(#19822457)
This isn't a general-case solution (because you can no longer just give someone a link), but, can't you send "s3.amazonaws.com" or really any other bucket name in the SNI and give the full bucket name in the Host header inside the encrypted channel? Or does S3 block SNI/Host mismatches?
[ Parent
| on HN ]
Re:Amazon S3 will no longer support path-style API requests
by agwa on Friday May 03, 2019 @05:48PM
(#19822595)
This currently works, but considering their crackdown on domain fronting last year, I don't expect it to work for much longer.
Re:Amazon S3 will no longer support path-style API requests
by tedunangst on Friday May 03, 2019 @05:46PM
(#19822585)
They will possibly block mismatches (I believe they do for cloudfront etc. now), but also if the point of moving to sub domains is sharding, there's no guarantee the bucket you want is behind the faked hostname you connected to.