They also removed support for mandatory features of HTTPS [0], as defined in RFC 2818. Not that I'm against the change /per se/, but there correct way to go ab

They also removed support for mandatory features of HTTPS [0], as defined in RFC 2818. Not that I'm against the change /per se/, but there correct way to go about it is to change the standard. They also claimed Firefox was doing the same thing, which is false and not really sufficient justification for not supporting things that MUST be supported. [0] https://bugs.chromium.org/p/chromium/issues/detail?id=700354 https://bugs.chromium.org/p/chromium/issues/detail?id=700354