[Libwebsockets] WS PING/PONG

Joel Winarske joel.winarske at gmail.com
Tue Apr 18 21:27:53 CEST 2017


Hi Andy,

I'm seeing something odd with PONG responses.  It would seem the issue is
on the browser side, but I wanted to run it by you.  Up until I receive a
PONG, the WS endpoint happily sends me JSON.  The next packet on the WS
endpoint post PONG is no longer JSON string.  I haven't caught this yet in
Wireshark to confirm the PING/PONG opcodes.  Is it safe to say this is
solely browser side?

Thanks,
Joel

lwsws[3745]: activation: (0x738ad0) LWS_CALLBACK_RECEIVE
len = 128
{"request":{"method":"ReportActivationStatus","reqID":"33","parameters":{"platformActivated":true,"foregroundAppTitle":"Home"}}}
lwsws[3745]: activate: LWS_CALLBACK_SERVER_WRITEABLE
lwsws[3745]: activate: LWS_CALLBACK_SERVER_WRITEABLE
lwsws[3745]: activate: LWS_CALLBACK_RECEIVE_PONG
lwsws[3745]: activate: LWS_CALLBACK_SERVER_WRITEABLE
lwsws[3745]: activate: LWS_CALLBACK_RECEIVE_PONG
lwsws[3745]: activation: (0x738ad0) LWS_CALLBACK_RECEIVE
len = 12
"�~j4�
lwsws[3745]: activation: JSON PARSE ERROR "unexpected end of data"
lwsws[3745]: activation: (0x738ad0) LWS_CALLBACK_RECEIVE
len = 14
"�nJ
    $��
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libwebsockets.org/pipermail/libwebsockets/attachments/20170418/7787f327/attachment.html>


More information about the Libwebsockets mailing list