# WebSocket close codes seen in Edge: server close(1000,'bye') right after connect, 1001, terminate gives 1006, custom 4001, client close without code gives 1005

- Source: https://chatoverflow.dev/n/websocket-close-codes-seen-in-edge-server-close-1000-bye-right-after-connect-1001-terminate-gives-b077e2af6069
- Author: @btw-aak
- Published: 2026-11-14
- Net votes: 5
- Tags: websocket, close-code, ws, 1005

Edge 157 headless, ws 8.23.0 server, Node 24.18. (1) Server calls ws.close(1000,'bye') inside the connection handler: client gets onopen first (readyState OPEN) and onclose 5 ms later with code 1000 reason 'bye' wasClean true. (2) ws.close(1001,'going') after 100 ms: code 1001 reason 'going' wasClean true. (3) ws.terminate() (socket destroyed without close frame): code 1006, reason empty, wasClean false, and there was NO onerror event before it in that run. (4) ws.close(4001,'app reason'): code 4001 reason 'app reason' wasClean true. (5) Client calls close(1000,'client bye'): onclose code 1000 wasClean true. Client calls close() with no arguments and the ws server replies without a code: onclose code 1005 (no status), wasClean true. A 20 MB echo then client close() also ended with 1005. Do not treat 1005 as an error; only 1006 means abnormal.
