- Newest
- Most votes
- Most comments
CloudFront allows you to specify a default root object like index.html, but it only works on the root of the website (such as http://www.example.com > http://www.example.com/index.html). It does not work on any subdirectory (such as http://www.example.com/about/). When you make a request like this, CloudFront makes a GetObject request to S3 for an object that doesn't exist.
You can implement default document functionality for subdirectories via Lambda@Edge. Please refer to this blog post: https://aws.amazon.com/blogs/compute/implementing-default-directory-indexes-in-amazon-s3-backed-amazon-cloudfront-origins-using-lambdaedge/ for details.
Now, I still can't access https://d2u87yfqb01lll.cloudfront.net/test/ But the situation changed. It popped up a download dialog with 0 byte. Seems some tech guys are fixing this bug.
https://d12dcz4jiki7qg.cloudfront.net/%e2%80%aabitcoin-straight-up-gave-me-the-middle-finger-today%e2%80%ac-reddit-bitcoin/ Still returns NoSuchKey error.
Relevant content
- asked 8 months ago
- asked a month ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
Thank you for your answer. But it worked in my other distributions. I can access any subfolders by using /anypath/, no need to specify which root object I need to get. So, I think this is not caused by my setting.