Replies: 1 comment 2 replies
-
I have literally the same issue. Receiving these logs after running console: [HPM] Upgrading to WebSocket
console: [HPM] Upgrading to WebSocket
console: [HPM] Client disconnected with that {
"**": {
"target": "http://localhost:8000/",
"ws": true,
}
} |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to proxy a WebSocket connection from my app to my own server using a
.proxyrc
like this (on the newly released Parcel 2.0.0):However, it doesn't work properly. I get a bunch of errors like this from my dev server process:
On my WebSocket server, I can see that the requests are coming in and then disconnecting immediately. The Chrome console also shows an error:
WebSocket connection to 'ws://localhost:1234/api/socket?' failed: Invalid frame header
.Is this a known problem? I was looking at the http-proxy-middleware docs and wondering if I'm failing to handle the WebSocket upgrade properly. But the way the docs say to handle it requires access to the Express server, which doesn't seem available even when you use a
.proxyrc.js
...Beta Was this translation helpful? Give feedback.
All reactions