Hacker News Reader

> To this day I still dont know why WebSockets and SSE dont support sending headers on the initial request

Doesn't the initial request get to send a full set of standard HTTP headers, cookies and all?

It does, but if you're calling it from the browser you can't add arbitrary data to them (the way you can in e.g. a `fetch`)

Someone at Azure thought of this[1]

> you can't add arbitrary data to them

What about intercepting the request with a service worker?