sockjs: WebSocketSession not yet initialized about http-proxy-middleware HOT 8 CLOSED

If your server is virtual hosted, try it with the option: changeOrigin: true

    proxy = proxyMiddleware('/go', {
        target: 'http://localhost:8080/',
        ws: true,
        changeOrigin: true
    });

from http-proxy-middleware.

It is a local Tomcat running a java app and hosting the socket. I tried changeOrigin, that gave me:

WebSocket connection to 'ws://localhost:3000/go/xxxxxxxxx/websocket' failed: Connection closed before receiving a handshake response 

from http-proxy-middleware.

Maybe you can leave out ws:true from the options or set it to ws:false, since you are explicitly upgrading with server.on('upgrade', proxy.upgrade);

from http-proxy-middleware.

I think that actually works! Thank you @chimurai

from http-proxy-middleware.

Glad to hear the solution works! :)

from http-proxy-middleware.

@elijahiuu Now that I think about it, this might be a bug...

I'll have to spend some time to investigate this.

from http-proxy-middleware.

+1 Having same problem, and seeing:

WebSocket connection to 'ws://localhost:9000/pubsub' failed: Invalid frame header

removing the line ws: true from proxy options seems to fix it.

I agree it is either a bug, or usage documentation needs to be updated.

from http-proxy-middleware.

@sashadt @elijahiuu

Think I've found the issue...

I published a beta version: v0.15.1-beta.
You can get it with: npm install [email protected]

Can you test it to confirm the fix?

Problem shouldn't occur anymore when the following are used:

// proxy config
config.ws: true

// external upgrade
server.on('upgrade', proxy.upgrade); 

from http-proxy-middleware.