Sure. If you need http header / cookie based auth with websockets, then you need the full http request with all the headers intact. This is the common case or at least something for which it is pretty straight forward to architect for.
Authenticating a websocket is just as easy as authenticating a regular http request. Because it is exactly the same.
Authenticating a websocket is just as easy as authenticating a regular http request. Because it is exactly the same.