4 ms·
As they discuss, will proxies have to specifically enable Web Sockets to allow this to replace AJAX? I thought this was the same problem Flash sockets had, tra
by Jasber 17y ago
As they discuss, will proxies have to specifically enable Web Sockets to allow this to replace AJAX?
I thought this was the same problem Flash sockets had, traffic being blocked.
- TimothyFitz 17y agoYeah, I have absolutely no idea why Web Sockets aren't just an initial HTTP request and then a protocol switch (Upgrade header); that would work for the vast majority of proxies and make cookies/same domain/etc work seamlessly.
- mcav 17y agoFrom the web socket spec: The protocol has two parts: a handshake, and then the data transfer. The handshake from the client looks as follows: GET /demo HTTP/1.1 Upgrade: WebSocket Connection: Upgrade Host: example.com Origin: http://example.com WebSocket-Protocol: sample The handshake from the server looks as follows: HTTP/1.1 101 Web Socket Protocol Handshake Upgrade: WebSocket Connection: Upgrade WebSocket-Origin: http://example.com WebSocket-Location: ws://example.com/demo WebSocket-Protocol: sample
- TimothyFitz 17y agoWell, that explains my disbelief. Thanks!
- daleharvey 17y agoI think the biggest problem with flash sockets was the flash part :)
- adatta02 17y agothe biggest problem with flash sockets is the insane security policy file business.