Comment 2 for bug 1217011

Revision history for this message
Richard Harding (rharding) wrote :

This is only in Chrome version 30 so far. The Firefox nightly hit was a mistake.

This is verified to be ok on juju-core.

Sample ws request:

Request URL:wss://10.0.3.96/ws
Request Method:GET
Status Code:101 Switching Protocols

Request
Cache-Control:no-cache
Connection:Upgrade
Cookie:__utma=1.898063223.1377539297.1377539297.1377539297.1; __utmb=1.3.9.1377539306979; __utmc=1; __utmz=1.1377539297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none)
Host:10.0.3.96
Origin:https://10.0.3.96
Pragma:no-cache
Sec-WebSocket-Extensions:x-webkit-deflate-frame
Sec-WebSocket-Key:8p+10Pzf+daA7BbDhAcBCw==
Sec-WebSocket-Protocol:undefined
Sec-WebSocket-Version:13
Upgrade:websocket
User-Agent:Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/30.0.1599.14 Safari/537.36

Response
Connection:Upgrade
Sec-WebSocket-Accept:7XfoEXkHml6D/OBV5t3/kCu5bLc=
Sec-WebSocket-Protocol:undefined
Upgrade:websocket

It's verified to also throw the same error on pyjuju.

Error: WebSocket connection to 'wss://10.55.32.3/ws' failed: Error during WebSocket handshake: Sec-WebSocket-Protocol mismatch

Request URL:wss://10.55.32.3/ws
Request
Cache-Control:no-cache
Connection:Upgrade
Cookie:__utma=1.1873839766.1377543376.1377543376.1377543376.1; __utmb=1.1.10.1377543376; __utmc=1; __utmz=1.1377543376.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none)
Host:10.55.32.3
Origin:https://10.55.32.3
Pragma:no-cache
Sec-WebSocket-Extensions:x-webkit-deflate-frame
Sec-WebSocket-Key:TPAABgqUlgVj9zSnF804tA==
Sec-WebSocket-Protocol:undefined
Sec-WebSocket-Version:13
Upgrade:websocket
User-Agent:Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/30.0.1599.14 Safari/537.36