Closed lukasgeyer closed 7 years ago
Is it maybe needing https://github.com/warmcat/libwebsockets/commit/586e42a827dd222b48ce21aceec88ed8cfd19f2d ?
Yes, thanks, this seems to solve the problem. I can confirm that ping is working using master at be9fb91 (which includes 586e42a).
What is the best option to get this commit into a stable branch on our end, is it possible to cherry-pick 586e42a on top of v2.1.0
? Or is there any official release planned in the near future (I could not find any planned milestone)?
You should follow v2.1-stable
https://github.com/warmcat/libwebsockets/commits/v2.1-stable
...if you want to stay on v2.1.
Any relevant fixes are already backported when the fix is made, including this one. Only fixes go on those branches, no new features.
When no subprotocol is used on a client connection (more specifically if the
protocol
oflws_client_connect_info
isnullptr
or does not match any protocol inprotocols
oflws_context_creation_info
), which is quite fine according to RFC 6455 1.9, the automatic sending of ping usingws_ping_pong_interval
does not work.This seems to be because
same_vh_protocol_list
is empty when iterating over the virtual hosts inlib/service.c:744
.Is this working as intended? If so, what is the preferred way of using ping when no subprotocol shall be used?