3 ms·
This may be because it's common for load balancers / reverse proxies to strip the TLS off before handing it to the back end (which may not even support WS over
by gnode 8y ago
This may be because it's common for load balancers / reverse proxies to strip the TLS off before handing it to the back end (which may not even support WS over TLS).
If the TLS encapsulated WS removed the XOR mask, it would require such a reverse proxy to add it on, rather than blindly forward the connection.
- olliej 8y agoCorrect, the problem is edge routers unwrapping and inspecting tls packets before forwarding to the internal network. So it’s not wasted due to tls. I mean it’s still a dumb waste of cpu cycles to support unfixed/unfixable routers, but there isn’t really a choice. Womp womp.