You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying IXWEbSocket sample code and I setup server and client successfully. The client tries to connect to server at wss endpoint "wss://localhost:8008", but I am getting this error from the server:
I inspected the attached main_server.docx. It constructs and starts a WebSocketServer without enabling TLS on the listener. -DUSE_TLS=1 compiles TLS support; it does not turn each server into a TLS listener. A TLS ClientHello sent to that plain listener is then interpreted as an HTTP request, explaining the “Invalid HTTP method” error.
Before server.listen(), configure the server certificate/key and enable TLS:
For a private/self-signed CA, configure the client's caFile with the issuing CA and use a wss:// hostname covered by the certificate. #654 adds these C++11 examples and clarifies the build-option/listener distinction. Current TLS server/client tests pass with OpenSSL and Mbed TLS, and Network.framework's TLS tests pass as well.
Closing this configuration issue; if it persists with TLS explicitly configured on the listener, please reopen with the current configuration and version.
Activity
peterphonic commentedon Jan 11, 2023
Did you create your key and certificate?
bsergean commentedon Nov 17, 2026
I inspected the attached
main_server.docx. It constructs and starts a WebSocketServer without enabling TLS on the listener.-DUSE_TLS=1compiles TLS support; it does not turn each server into a TLS listener. A TLS ClientHello sent to that plain listener is then interpreted as an HTTP request, explaining the “Invalid HTTP method” error.Before
server.listen(), configure the server certificate/key and enable TLS:For a private/self-signed CA, configure the client's
caFilewith the issuing CA and use awss://hostname covered by the certificate. #654 adds these C++11 examples and clarifies the build-option/listener distinction. Current TLS server/client tests pass with OpenSSL and Mbed TLS, and Network.framework's TLS tests pass as well.Closing this configuration issue; if it persists with TLS explicitly configured on the listener, please reopen with the current configuration and version.