[ws server]: doesn't reply with HTTP response on bad websocket HTTP upgrade request.

[99Kies]

parachain version: 0.9.22
start command:

parachain-node --collator --chain ksm-mainnet.json --base-path /data \
 --port 3033  --ws-port 9944 --unsafe-ws-external --rpc-cors all \
 -- --execution wasm --chain kusama.json

The previous websocket supports http access.

After upgrading to 22, websocket no longer supports http access.

[niklasad1]

Hey @99Kies

Are you expecting a proper HTTP response to the HTTP request?
The request will fail to initiate the WebSocket handshake and it's just dropped on our side I think.

Should be quite easy to fix though, are you using this to find out when the websocket server has been started?

[99Kies]

Hey @99Kies

Are you expecting a proper HTTP response to the HTTP request? The request will fail to initiate the WebSocket handshake and it's just dropped on our side I think.

Should be quite easy to fix though, are you using this to find out when the websocket server has been started?

Yes, we will try to check if the service is healthy via the HTTP protocol. I think this is also necessary.

---

We will regularly use this method to judge whether the service of 9944 is normal.

curl -ikv localhost:9944

[niklasad1]

It's bit "expensive" to open a WS connection for that everytime.

Recently, we added server-side pings to WS Server which is enabled in polkadot v0.9.25. The server will send out a pings periodically every 30s if it's "healthy" and it might be easier for you to just listen on those instead of opening a new connection all the time.

However, we should fix it anyway thanks for reporting the issue.

[tinydjp]

Hi @niklasad1 as we're using AWS to run our nodes, it seems that only ALB can support the wss protocol. In that case, ALB can only use HTTP(S) to run health check. We tried to use Network Load Balancer, the health check succeeded with TCP, but failed to connect via ws/wss.

[niklasad1]

Alright, I see.

This will fixed by #819 anyway

[niklasad1]

Closed by #819