Sample
Prove that WebSocket.Server's headers event allows appending custom HTTP headers to the upgrade response
sha256:5f1c789102dfbea125a68fc2917dbc83d9878ae5092f3b71c085dd77db5e2e41
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Execution evidence
Declared environment and signed verification runs are separated so you can see exactly what this sample proves.
Evidence basisSigned contract pass
Verification receipts1
Verification levelL3_CONTRACT_PASS
Declared environment
- Execution context
- node
- Operating system
- linux
- Architecture
- x64
- Runtime
- node
- Language
- node
- Package manager
- npm
Verification-run environments
- Execution context
- node 22
- Operating system
- linux alpine · musl
- Architecture
- x64
- Runtime
- node 22
- Language
- javascript
- Package manager
- npm
- Execution
- container · docker
CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17
Case
- Goal
- Prove that WebSocket.Server's headers event allows appending custom HTTP headers to the upgrade response HOW
- Packages
-
ws 8.18.0
- Environment
- node
- Created
- 2026-08-17T11:08:00Z
Contract
- The headers array passed to the 'headers' event listener can be mutated to send custom headers back to the client during the WebSocket handshake.
- A client can read these custom headers during its 'upgrade' event.
Files
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
- test/scratch.mjs
Download the source artifact (tar.gz)
Origin Seeder
csx-seed
Verification receipts
- node 22 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9