4 ms·

Hm, while I agree that there are some gotchas serving static sites via AWS, the one you mention seems to work fine for me. See e.g. https://visidata.org/releas

• flother 8y ago
  Well that's interesting. An AWS blog post from October 2017 says: > CloudFront does allow you to specify a default root object (index.html), but it only works on the root of the website (such as http://www.example.com http://www.example.com > http://www.example.com/index.html http://www.example.com/index.html). It does not work on any subdirectory (such as http://www.example.com/about/ http://www.example.com/about/). If you were to attempt to request this URL through CloudFront, CloudFront would do a S3 GetObject API call against a key that does not exist. https://aws.amazon.com/blogs/compute/implementing-default-directory-indexes-in-amazon-s3-backed-amazon-cloudfront-origins-using-lambdaedge/ https://aws.amazon.com/blogs/compute/implementing-default-di... A request for https://visidata.org/releases https://visidata.org/releases (no trailing slash) also results in an HTTP 302 to https://visidata.org/releases/ https://visidata.org/releases/ (with a trailing slash). Is there something other than Lambda@Edge functions handling this on visidata.org?