Here is the readable text from the wireshark capture. The request that works looks like this
Apache running HTTPS talking to tomcat on port 8080 (non-ssl) E@@I Q QmiPGET /alert/event HTTP/1.1 Host: ###.com Origin: https://###.com Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: vPVEY5WCf17Od94k+c/MpQ== Sec-WebSocket-Version: 13 Sec-WebSocket-Extensions: x-webkit-deflate-frame X-Forwarded-For: 10.81.1.12 X-Forwarded-Host: ###.com X-Forwarded-Server: ###.com Upgrade: WebSocket Connection: Upgrade us-cli > 27905 [ACK] E@@` Q Qmi+P 5HTTP/1.1 101 Switching Protocols Server: Apache-Coyote/1.1 Upgrade: websocket Connection: upgrade Sec-WebSocket-Accept: aYYtgKFlU/vrt/MCQ9EQHlPQY5c= Date: Tue, 02 Apr 2013 13:45:07 GMT the request that fails looks like this Apache running HTTPS forwarding to tomcat on 8443 (SSL) Eh@@ Q Q 1N,BgPGET /alert/event HTTP/1.1 Host: ###.com Origin: https://###.com Pragma: no-cache Cache-Control: no-cache Sec-WebSocket-Key: OfRlq1skxYe1Z0EqD5u9Hg== Sec-WebSocket-Version: 13 Sec-WebSocket-Extensions: x-webkit-deflate-frame X-Forwarded-For: 10.81.1.12 X-Forwarded-Host: ###.com X-Forwarded-Server: ###.com Upgrade: WebSocket Connection: Upgrade pcsync-https > 44249 [ACK] pcsync-https > 44249 [PSH, ACK] 44249 > pcsync-https [ACK] pcsync-https > 44249 [FIN, ACK] 44249 > pcsync-https [ACK] It's obvious the upgrade is not happening but I don't know where to look for why. Again any information is appreciated. On Mon, Apr 1, 2013 at 8:11 PM, Jamie Johnson <[email protected]> wrote: > Changing from 8443 to 8080 everything works as expected so my assumption > is yes. I will try to grab the packets to verify > On Apr 1, 2013 7:52 PM, "Eric Covener" <[email protected]> wrote: > >> Are you sure the other end is speaking websockets? A packet capture >> might confirm which side complained first / wrongly. >> >
