-
Notifications
You must be signed in to change notification settings - Fork 85
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
WebSocketException: Not GET request #104
Comments
Hi, Is it a self-signed certificate? Does it work when you use it with HTTPS? Cheers. |
Hello, yes, this is a self-signed certificate. Apache httpd ssl working with this sertificate (converted to pem/key). For Web-Socket hub in the project i use pfx (p12) format and password. // sincerely, alex |
The browser needs the user to accept that certificate, are you using it for HTTPS as well in the same page that is initiating the WebSocket connection? |
Yes, in opening the page browser (chrome) write about self-signed certificate ( and allow to select "Continue with this certificate..". I press it and continue to working with page. // sincerely, alex |
Have you tried with these approaches? https://stackoverflow.com/questions/18462064/associate-a-private-key-with-the-x509certificate2-class-in-net/24863777#24863777 |
Yes, i convert *.pem certificate to *.p12 using openssl unix-utility But now i see that it's working without any problems if i use not self-signed certificate.. So it can be certificate problem. For converting normal certificate i have used same way. It's possible if problem with certificate, WebSocketLibrary have a wrong request string? // sincerely, alex |
fyi. I get this when my certificate expires |
Hello! I have a next exception when client try to connect to listener by wss:
Code for creating listener was used from examples.
SSL feature enabling code:
Thank You in advance!
// alex
The text was updated successfully, but these errors were encountered: