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
My issue is when am having two pvo : lws-minimal-server-echo, default (snippet above) I can use both webserver and websocket
but while serving WEB pages getting ERR_CONNECTION_CLOSED after loading few files
If I keep only one pvo for the websocket callback,
The webserver load performance is stable but the websocket connection gets open but SEND/RECEIVE does not happen (testing with simple web client)
Creating context as below:
Protocols defined looks like this:
Any guidance will help.
Thanks
The text was updated successfully, but these errors were encountered:
... lws send out a lot of logs you can use to understand its point of view. You're going to have to look at them...
The commented pvo's job is to tell lws how to route a NULL protocol name request for ws upgrade, in terms of which protocol on the lws side. If the browser side doesn't provide a protocol name with its request, you need to use it to bind the ws connection to the expected protocol / callback.
Hi Andy,
Am using HTTPS and WSS both at port 443,
My issue is when am having two pvo : lws-minimal-server-echo, default (snippet above) I can use both webserver and websocket
but while serving WEB pages getting ERR_CONNECTION_CLOSED after loading few files
If I keep only one pvo for the websocket callback,
The webserver load performance is stable but the websocket connection gets open but SEND/RECEIVE does not happen (testing with simple web client)
Creating context as below:
Protocols defined looks like this:
Any guidance will help.
Thanks
The text was updated successfully, but these errors were encountered: