© 2026 Hedgehog Software, LLC
Twitter
GitHub
Discord
System
Light
Dark
More
Communities
Docs
About
Terms
Privacy
Search
Star
Feedback
Setup for Free
websocket when added "upgrade" header, not being sent in headers while api is called - Cloudflare Developers
CD
Cloudflare Developers
•
2y ago
•
5 replies
raj.js
websocket when added "upgrade" header, not being sent in headers while api is called
client
c
o
d
e
:
-
let resp
: any
= await fetch
(
"
http://127.0.0.1:8787
"
,
{
headers
:
{
Upgrade
:
"websocket
"
,
}
,
}
)
;
let ws
= resp
.webSocket
;
if
(
!ws
)
{
throw new Error
(
"server didn
't accept WebSocket
"
)
;
}
worker
c
o
d
e
:
-
export default
{
async fetch
(request
: Request
, env
: Env
, ctx
: ExecutionContext
)
: Promise
<Response
>
{
const upgradeHeader
= request
.headers
.get
(
'Upgrade
'
)
;
if
(
!upgradeHeader
|
| upgradeHeader
!
=
=
'websocket
'
)
{
return new Response
(
'Expected Upgrade
: websocket
'
,
{ status
: 426
}
)
;
}
headers does not include Upgrade header
. is it something related to workers
?
Cloudflare Developers
Join
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
86,942
Members
View on Discord
Resources
ModelContextProtocol
ModelContextProtocol
MCP Server
Similar Threads
Was this page helpful?
Yes
No
Recent Announcements
Similar Threads
websocket headers
CD
Cloudflare Developers / workers-and-pages-help
3y ago
websocket request to durable object does not contain upgrade header
CD
Cloudflare Developers / workers-and-pages-help
2y ago
Route not being added
CD
Cloudflare Developers / workers-and-pages-help
7mo ago
Error: internal error when replied to a get request with websocket upgrade headers with a websocket
CD
Cloudflare Developers / workers-and-pages-help
3y ago