Earlier quoted context omitted.
> 4. Trying to get www.dontwordle.com and dontwordle.com to take you to the same URL (either www.dontwordle.com or dontwordle.com) and still support TLS and only use the tech I mentioned above. I actually still don’t have it working perfectly. I know of a solution, but it’s overly complicated If you use Cloudfront with an S3 bucket as origin for _dontwordle.com_, just create a second Cloudfront with an S3 Bucket for…
So you can do this, but it won't support TLS to my knowledge. At least in my testing, it will work to navigate to www.dontwordle.com (you will get redirected to https://dontwordle.com ). However, if you tried navigating _directly_ to https://www.dontwordle.com , that would not work. In fact, you can try clicking on https://www.dontwordle.com right now, and it won't work :) To be fair, currently I do not have it imple…
It was some tinkering around with bucket name (has to match the subdomain.domain.tld) and the cloudfront origin settings. But it works flawlessly. Feel free to ping me if you need details.
See links below.
coindex.de www.coindex.de