3 ms·
In my case, the problem is not browsers but vendor-provided enterprise tools. When HTTP became the “new tcp”, all sorts of things started using it behind the sc
by toyg 7y ago
In my case, the problem is not browsers but vendor-provided enterprise tools. When HTTP became the “new tcp”, all sorts of things started using it behind the scenes. Eventually someone added support for ssl/tls, but now we have to wait for $vendor to support any protocol upgrade.