Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(1)

Issue 10946007: Never send reserved status codes in a close frame (Closed)

Created:
8 years, 3 months ago by Søren Gjesse
Modified:
8 years, 3 months ago
Reviewers:
Anders Johnsen
CC:
reviews_dartlang.org
Visibility:
Public.

Description

Never send reserved status codes in a close frame When receiving a close frame with no status code the reported status code is 1005. If the close is echoed as part of the close handshake the echoed close frame must also have no status code and NOT status code 1005. The description of status code 1005 from the spec: 1005 is a reserved value and MUST NOT be set as a status code in a Close control frame by an endpoint. It is designated for use in applications expecting a status code to indicate that no status code was actually present. R=ajohnsen@google.com BUG=dart:5209 Committed: https://code.google.com/p/dart/source/detail?r=12482

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+31 lines, -6 lines) Patch
M runtime/bin/websocket.dart View 1 chunk +5 lines, -1 line 0 comments Download
M runtime/bin/websocket_impl.dart View 3 chunks +14 lines, -1 line 0 comments Download
M tests/standalone/io/web_socket_test.dart View 4 chunks +12 lines, -4 lines 0 comments Download

Messages

Total messages: 2 (0 generated)
Søren Gjesse
8 years, 3 months ago (2012-09-18 09:15:42 UTC) #1
Anders Johnsen
8 years, 3 months ago (2012-09-18 10:25:59 UTC) #2
LGTM

Powered by Google App Engine
This is Rietveld 408576698