Websocket connection failed - invalid frame header

[totojack]

Hi.

I'm trying to debug this error from chrome web browser. These are some details of the application stack:

• web server: apache httpd 2.4 (proxying to app server using ws proxy module)
• application server: apache tomcat 8.5
• java webapp with spring websocket and stomp js used in the ui
• websocket request using http port

I've attached an image of chrome dev tools with frames related to the failing ws request, and one of them is the cause of the error. Can you give me some advise? Should it depend on services stack? I don't see errors on application server nor on web server. Same problem on firefox.

Thanks Luca

[dazed19]

Hi - I realise this is slightly old.

We had similar problem to this using Apache HTTPD 2.4 as included in base Linux via yum install (using RedHat or Oracle EL to be explicit).

To resolve this we had to build from source to get WebSocket support resolved - we ended on 2.4.25 - but I think fixed in earlier patch - the issue (I think) is that on RHEL v7 httpd is functionally stuck at 2.4.6 with security patches only applied.

I might suggest (to prove it's apache) you test with by pypassing httpd - I used an SSH Tunnel into app server to do this e.g. "ws://localhost:8080/"

[alifellod]

It seems to be related to the browser, and the frequency of sending, packet size related