Sec-Websocket-Protocol response, perhaps with custom upgrader about centrifuge HOT 3 CLOSED

@vladvelici hello!

First of all - have you considered using JWT authentication over built-in library JWT support?

I mean that on client side you can set JWT with

centrifuge = new Centrifuge(...);
centrifuge.setToken('<JWT>');

where JWT should follow rules described here - https://centrifugal.github.io/centrifugo/server/authentication/

?

from centrifuge.

Hi! I didn't actually see that before. I saw some JWT related stuff but I didn't notice it was for exactly this purpose. I probably can remove my auth middleware and just use this instead but it'll have to wait until I make the changes (other pressing issues first).

Thank you for the quick reply!

I don't really need to be able to specify the header anymore assuming the JWT stuff here works as I think it does. I'm closing this issue (I hope that's OK, doesn't seem needed anymore) - thanks again for the reply.

from centrifuge.

@vladvelici feel free to reopen if it wont work for you. BTW if current JWT format does not fit your case there is also a way to do custom JWT parsing and authentication inside ClientConnecting callback.

from centrifuge.