-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set custom headers on WSS connection #22
Comments
Hi, thanks! I'm glad you like the library and find it useful. It's not possible at the moment, but it won't be very difficult to add. Give me 24 hours (max) and it will be ready! Best regards, |
24hs max!!!!! you are my idol !!!!!! Thanks!!!!! |
Added addHeader method to WebsocketsClient as suggested in issue #22
How about 4 hours max 😃 Thanks for the kind words, Iv'e added an Example: client.addHeader("Authorization", "JWT [token]"); Wait for version 0.4.8 (it will be in the IDE soon, you can also get it as ZIP). Thanks again for using the library, give it a star if you liked it so more users can notice it. Let me know that you have used the new version and that everything works fine for you. Have an awesome weekend, |
Hi Gil, thanks for your time. For some reason do not work. I have another example made with another library (Links2004), and works ok, but with your example Y can not obtain the websocket. I will make furter test to find the diference and tell you. Regards!!!! |
That's odd. Can you show me your code? |
Hey Gil (@gilmaimon), cool new feature, I was also looking for this! @mmcArg - make sure you're not behind a proxy server which does not forward the headers; may be the case. And also, this must be called BEFORE Keep up the good work, Best, |
Awesome as always. Thanks Adelin! Gil. |
Hi!!!, first of all, the library is great!!!!, and sorry for my english.
I am working with a server that requires a token in connection header ("Authorization: JWT [token]") to accept the connection of websocket. Is possible to add a custom header in header request?
The text was updated successfully, but these errors were encountered: