Skip to content
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

Webserver and Websocket at same port , Serving pages gets timed OUT #3237

Open
Somritag opened this issue Oct 3, 2024 · 1 comment
Open

Comments

@Somritag
Copy link

Somritag commented Oct 3, 2024

Hi Andy,

Am using HTTPS and WSS both at port 443,

image

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
image

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:
image

Protocols defined looks like this:
image

Any guidance will help.
Thanks

@lws-team
Copy link
Member

lws-team commented Oct 4, 2024

... 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants