7 Apr
2015
7 Apr
'15
12:04 p.m.
Daniel-Constantin Mierla writes:
yes, i missed it.
forgot to
include an example of a GET request from the tunnel:
GET / HTTP/1.1.
Host: 192.98.102.30:8000.
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0
Iceweasel/31.6.0.
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8.
Accept-Language: en-US,en;q=0.5.
Accept-Encoding: gzip, deflate.
DNT: 1.
Sec-WebSocket-Version: 13.
Origin: https://test.tutpro.com.
Sec-WebSocket-Protocol: sip.
Sec-WebSocket-Key: NKwlVvwJcj2Z07MlXm8URg==.
Pragma: no-cache.
Cache-Control: no-cache.
X-Forwarded-For: 192.98.103.30.
X-Forwarded-Host: 192.98.103.33.
X-Forwarded-Server: jessie.test.tutpro.com.
since Connection, Upgrade and Sec-WebSocket-Version headers are missing,
it looks to me that a modified version of ws_handle_handshake() would be
needed.
I see Sec-WebSocket-Version header. Anyhow, if upgrade header is missing, isn't this
just going to be bare
http(s) connection?
Or what is apache expecting to happen? To still
upgrade to websocket?
i don't think so, but perhaps it should still include
Sec-WebSocket-Accept header in 101 reply and add the connection to
Websocket connection table?
-- juha