Hacker News new | ask | show | jobs
by richardwhiuk 3619 days ago
But the other point is that https now means HTTP/2 or HTTP/1.1, where as http always mean HTTP/1.1 - so I'm not sure that's true.
2 comments

If https can mean one of two things, but http2 clearly means only one thing, why would anybody choose to use the term https unless they are trying to be deceptive?
Or of they're trying to refer to the thing that http2 is not?
https and HTTP/2 are not the same thing, though. Until HTTP/2 traffic is the vast majority when compared to HTTP/1.1 with TLS, you can't claim https and HTTP/2 are the same.

For example, if you terminate your secure traffic on an AWS ELB (or using S3, or CloudFront), you are serving HTTP/1.1 with TLS. And will be for the foreseeable future.

Can you point me to the RFC where https was redefined to not be HTTP/1.1 over TLS?
https was never defined in an RFC in the first place, as I understand it, it's just defacto used for that since Netscape started.