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
The RFC allows ping and pong frames to have payloads (up to 125 bytes), and requires that a pong for a ping contain the same payload as the ping. However, the current websocket/af API does not allow sending payloads with ping and pong frames:
Since anmonteiro/httpun-ws#36 was fixed
recently, websocket/af supports sending ping and pong payloads, as
required by the WebSocket spec. This commit has dream-httpaf using that
support.
See also #181.
The RFC allows ping and pong frames to have payloads (up to 125 bytes), and requires that a pong for a ping contain the same payload as the ping. However, the current websocket/af API does not allow sending payloads with ping and pong frames:
https://github.com/anmonteiro/websocketaf/blob/248a2cb0dcffa51996c3ad7643577dce75d67454/lib/websocketaf.mli#L151-L152
I actually don't know if ping/pong payloads are used in practice.
The text was updated successfully, but these errors were encountered: