Rebecca Murphey on HTTP/2’s encryption requirement:
HTTP/2 is a new protocol, and as such, it is greatly confusing to a large segment of the existing internet: proxies, antivirus software, and the like. During the development of HTTP/2 and SPDY before it, engineers observed that traffic that was transported on an insecure connection would frequently fail. The reason? The proxies, the antivirus software, and all the rest had certain expectations of HTTP traffic; HTTP/2 violated those expectations, and so HTTP/2 traffic was considered unsafe. The software that thwarted insecure HTTP/2 traffic didn't have the ability to inspect secure traffic, and so HTTP/2 traffic over a secure connection passed through just fine. Thus was born the requirement — which is a browser implementation detail, and not part of the HTTP/2 spec — that HTTP/2 web communication be conducted using TLS.
New OpenSSL, now waiting for PHP7 and Let’s Encrypt public beta 🙄
Tomorrow we should get PHP7 and the Let’s Encrypt public beta, bring it on.
This House of Commons Syria session has settled in to a quite civilised debate.
Please restore my faith in politics. #DontBombSyria
Oh wow that last note went wrong.
Should domains have trailing slashes, https://domains.com or https://domain.com/?
What a crap film 300: Rise of an Empire is
Pretty sweet new song from Coldplay.
Another morning @StartinSalford, busy place as usual 😊