Mar 10, 2014
Web sockets in 11.4
Hi guys!
Been getting more requests regarding Web sockets from our developers.
The way I've understood it is that the client will send a request to the LB over HTTP, the lb will choose a server ...
Hi!
Thanks for your reply! Been reading your replies here on Dev Central and learning alot from you. Your efforts are much appreciated!
Yeah, it's an interesting topic and feels a bit like fumbling in the dark. 🙂
Seems like the initial request gets a response with some upgrade headers (taken from here😞
ET /demo HTTP/1.1
Upgrade: WebSocket
Connection: Upgrade
Host: example.com
Origin: http://example.com
WebSocket-Protocol: sample
Server to client:
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
The initial request is bound to have some headers, but the following requests will go over web sockets (providing that the browser supports it), which does not contain headers. If there is not headers, there is not Set-Cookie, and without Set-Cookie, there is no cookies. You're right in that the initial request could have one, but it would not be there for the following requests?
In regards to SSL, I was reasoning like this: You need to have an HTTP profile to be able to use an SSL Client profile, and since the HTTP profile on a VS handling web sockets traffic would be there to support the initial request (and a fallback for clients not supporting WS?), I don't think it'd support accelerating WSS (Web Sockets Secure(?)). Check out this solutions article.
Some more articles from Lori MacVittie. Most likely a bit biased, but they make sense:
I'm gonna try to nip this one in the bud.
/Patrik