1. 1
    Chrome disables support for mandatory features of HTTPS browsers rant web rkeene.org
    rkeene avatar authored by rkeene 1 year ago | cached | 3 comments

  1.  

  2. 2
    jabberwock avatar jabberwock 1 year ago | link

    Firefox did this first with 48, released over 6 months ago.

    This just shows it doesn’t matter how long something is deprecated for, people will keep doing it until there’s a tangible reason for them not to.

    1. 1
      tedu avatar tedu 1 year ago | link

      Why are you still using a feature that’s been deprecated for 20 years?

      1. 1
        rkeene avatar rkeene 1 year ago | link

        Because the RFC (RFC 2818) says things doing HTTPS must support it and it’s slightly simpler.