-
-
Notifications
You must be signed in to change notification settings - Fork 81
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
Can't connect to websocket with authorization header #39
Comments
Hello @cleverClosure , |
Can I send it to you privately somehow? I don't want the url to be public |
You can send me an email : [email protected] |
I've sent you an email |
Hello again @cleverClosure, Can you provide a working authentication token or please check your server part :) |
Yes, that is exactly what I get when I use ws instead of wss or https. Here is the new token: 451ac7a5-ad93-4859-8c62-b41e96d6a34d |
The server side works, because I am able to connect to it from the web client |
@cleverClosure |
The webserver works on sockJS but adding /websocket to the url didn't help |
@cleverClosure I'm really sorry but I could not find the problem about your issue :( |
Can I ask you which websocket with auth did you try (the one you were able to connect successfully)? Is that local webserver or something? |
I've tried on a very simple local webserver. Unfortunately, I do not have any other options. |
Someone solved this problem? |
Same issue! Someone solved this ? |
@cedb777 @cleverClosure
|
@iOSDias Hi! It works? |
It worked for me with this code:
|
@said13 yes |
Finally, I closed the issue :) Please open a new one if you still have a problem. |
For the ones who could not make it using headers on connection, try this, that approach works on my environment. |
Hi. I get an error while trying to connect to websocket, here is the code:
Response:
Do you have any ideas why that might be the case?
The text was updated successfully, but these errors were encountered: