3 ms·
That's because quite a few of us shunt the folks trying to access port 80 back onto port 443 (usually by redirecting the request to the https:// https:// equiva
by yellowapple 12y ago
That's because quite a few of us shunt the folks trying to access port 80 back onto port 443 (usually by redirecting the request to the https:// https:// equivalent, be it in the load balancer, in the web server, or (in some cases) in the application/site itself).
The world's switching to HTTPS-only setups anyway (particularly when deploying JSON APIs, which are all the rage nowadays). Might as well be ahead of the curve.