Project

General

Profile

Bug #10287

wthttp does not acknowledge WS close

Added by Roel Standaert 7 months ago. Updated 7 months ago.

Status:
Closed
Priority:
Normal
Target version:
Start date:
05/03/2022
Due date:
% Done:

100%

Estimated time:

Description

When the client closes a WebSocket connection it sends a message with a close opcode.

According to RFC 6455 5.5.1: If an endpoint receives a Close frame and did not previously send a Close frame, the endpoint MUST send a Close frame in response.

Not sending the Close frame back would cause Firefox to exponentially back off. The result would be that if you would close many tabs at once with open WebSocket connections to the same endpoint, Firefox would immediately set the delay for new WebSocket connections to 1 minute. See this issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1608701

#2

Updated by Roel Standaert 7 months ago

  • Status changed from InProgress to Review
  • Assignee deleted (Roel Standaert)
#3

Updated by Roel Standaert 7 months ago

  • Target version set to 4.7.2
#5

Updated by Roel Standaert 7 months ago

  • Status changed from Review to Implemented @Emweb
  • Assignee set to Roel Standaert
  • % Done changed from 0 to 100
#6

Updated by Roel Standaert 7 months ago

  • Status changed from Implemented @Emweb to Resolved
#7

Updated by Roel Standaert 7 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF