Websocket connection failed, Invalid frame header

[dean5277]

Version

3.0.0-rc.3

Reproduction link

http://localhost:8080

Steps to reproduce

npm run serve

What is expected?

no error

What is actually happening?

when i run dev serve, brower console print socket error.

[LinusBorg]

You seem to be messing with the proxy with this proxyfile? But you don't share it.

We can't investigate you report without a proper, run able reproduction (as a guy repository)

Please provide one or we have to close this issue.

[dean5277]

proxyFile content.

[LinusBorg]

That's not a run able reproduction. I won't type the code from your screenshot to run it.

[rayax86]

I am running into this issue too. Basically, when the / path exist, HMR websocket requests are not ignored and will be somehow proxied. This can be disabled by adding ws: false to the options, however, this will disable all websocket requests.

[tomwang1013]

I am running into this issue too

[ChrisShen93]

+1

[dean5277]

proxytable key 'ws' set false, this will disable all websocket requests.

[ChrisShen93]

In my case, I use the following configuration to proxy websocket for my site:

proxys: {
  '/websocket': {
    target: my_ws_server,
    ws: true,
    changeOrigin: true
  }
}

It will cause the same problem like the issue said.

All what I do to resolve is to add a '^' :

proxys: {
  '^/websocket': {
    target: my_ws_server,
    ws: true,
    changeOrigin: true
  }
}

[rayax86]

@ChrisShen93 Cool, in which package does the ^ actually took effect?

[ChrisShen93]

@rayax86
Sorry for late reply.
That's for the http-proxy-middleware.

[cduyzh]

ws改为false

[tangdaohai]

Why set it to ws: false, it works?