+
Skip to content

websocket client not specifying a (sub)protocol fails to communicate with LWS server #3375

@gmabey

Description

@gmabey

In minimal-examples-lowlevel/ws-server/minimal-ws-server/, commenting out the lws_callback_http_dummy line (such that the server runs only one protocol) and connecting with the attached python script, the connection times-out, unless lws-minimal is passed as an argument.
I'm running this on Windows, on a commit out of main that is like 2 weeks old.
This behavior seems to be contrary to the documentation that reads:

Websockets allows connections to negotiate without a protocol name... in that case by default it will bind to the first protocol in your vhost protocols[] array.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载