Project

General

Profile

Actions
Copy link

Bug #10287

closed
RS RS

wthttp does not acknowledge WS close

Bug #10287: wthttp does not acknowledge WS close

Added by Roel Standaert over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Roel Standaert
Target version:
4.7.2
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

RS Updated by Roel Standaert over 4 years ago Actions
Copy link
 #2

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

RS Updated by Roel Standaert over 4 years ago Actions
Copy link
 #3

  • Target version set to 4.7.2

RS Updated by Roel Standaert over 4 years ago Actions
Copy link
 #5

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

RS Updated by Roel Standaert over 4 years ago Actions
Copy link
 #6

  • Status changed from Implemented @Emweb to Resolved

RS Updated by Roel Standaert over 4 years ago Actions
Copy link
 #7

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: PDF Atom