{"author":"Stefan Eissing","author_email":"stefan@eissing.org","author_time":1756994945,"commit_time":1757071059,"committer":"Daniel Stenberg","committer_email":"daniel@haxx.se","hash":"0b091328773c64e23f5c4739da74527093c6a5ab","message":"websocket: handling of PONG frames\n\nThe auto PONG frames were inserted into the connection at the time\na PING had been decoded, irregardless if an upstream frame was just\nin the middle of being assembled.\n\nAdd PONG frames only to the buffer if there is no frame currently\nassemebled and, if it is, set the control frame aside. This control\nframe is then added on the first opportunity of a \"clean\" send buffer.\n\nThere is only a single control frame set aside at a time. This means\na double PING will, when the PONG cannot be sent right away, only\nsend the last PONG.\n\nI imagine this is fine. We want to prevent the endless buffering of\nPONG frames on a connection where the server sends but does no receives.\n\nReported-by: Calvin Ruocco\nFixes #16706\nCloses #18479\n","parents":["4c0da282313be92bc608fbef3dc5e37618c53052"],"tree_hash":"570549ef3a2fd7c524d3e26299a15dec81549c55"}