Hacker News Reader

Comment by Alex3917 | Hacker News Reader

For what it's worth, here is the original thread:

https://news.ycombinator.com/item?id=13011120

This should definitely meet our needs in both cases: serving prerendered content when necessary, and also adding the security headers to the front end. And it's definitely a 10x better solution than having an extra EC2 instance with your private certs on it, just to run an nginx proxy with twenty lines of code.

View on HN

Although you will have to shell out 600$/Month if you need to support HTTPS for browsers that do not support SNI

Which is everything but IE6 right?

It's not supported in IE 6 on any OS, or any IE version on Windows XP or before (has to be supported by both the browser and the underlying network stack). Also not supported on Android < 3.x.

Most companies I've worked with in the past year or so have made the decision that SNI support is good enough and have switched.

Wait, by "original thread" are you implying this feature was thrown together in the past week and a half since you asked that question?

Yes, the HN thread is prominent in the article.

Ah, OK: the answer is "no" (as the question did not lead to the feature), not "yes" ;P; and also "I am dumb" (FWIW, I actually got to this thread by searching for it after already knowing about @Edge, so I didn't even click the article link: I saw the @Edge stuff today in the ECS FAQ, searched for it on Google and saw it had been announced 15 minutes earlier, and then came to HN to read comments about it).

Of course not. But it still explains what this new feature does that AWS wasn't able to do previously.

>Without spilling any beans I let him know that we were very aware of this use case and that we had some interesting solutions in the works. Other customers have also let us know that they want to customize their end user experience by making quick decisions out at the edge.

It was in the pipeline already I guess.

Reply on news.ycombinator.com