3 ms·
The intention of the WebSocket protocol is that the handshake is sufficiently unlike HTTP that nobody could make a meaningful response to it by mistake. As for
by geofft 12y ago
The intention of the WebSocket protocol is that the handshake is sufficiently unlike HTTP that nobody could make a meaningful response to it by mistake.
As for non-meaningful responses, isn't this equivalent to using <img src="http://192.168.1.1/admin?action=evil"> http://192.168.1.1/admin?action=evil"> to send an HTTP request? That's also not restricted by same-origin, and never has been and never will be. You get the same result -- you cause an HTTP request to be sent somewhere, and the response isn't useful to you nor is the contents of the response visible to you, but the request and its side effects still happen.
I'm not super well-versed in websocket design, so I'm happy to be convinced I'm wrong, but that's my understanding of why it works the way it does.
- jessaustin 12y agoAhhh, you're right. I guess this just ends up being another way of "fingerprinting" the hosts on the local network, which really is kind of minor.