There’s an additional RTT (TLS 1.3) or two (TLS ≥ 1.2) with HTTPS, and there’s no security gain to be had if the page is server over HTTP anyway.
@Dieulot Might I suggest changing
src="//instant.page/1.1.0"
into
src="https://..."
There's no reason not to use HTTPS explicitly when it's available, and not doing so is an anti-pattern. See https://www.paulirish.com/2010/the-protocol-relative-url/ ….
-
-
-
That last claim is provably false.https://github.com/konklone/cdns-to-https#conclusion-cdns-should-redirect-to-https …
- 3 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.