Websocket doesn't send close-frame as defined by RFC6455 5.5.1
Reported by
dimitrio...@googlemail.com,
Feb 4 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce the problem: I build a websocket-server and the client doesn't send any close-frame when calling WebSocket.close(); What is the expected behavior? Close-frame needs to be send when attempting to close the connection. The recieving end needs to send a close-frame aswell. After sending AND recieving a close-frame, the endpoint may close the TCP-connection What went wrong? No close-frame Did this work before? No Chrome version: 56.0.2924.87 Channel: stable OS Version: 6.3 Flash Version: Shockwave Flash 24.0 r0
,
Feb 6 2017
,
Feb 7 2017
Could you provide a net-internals log[1]? Also, do you see the issue with other browsers? 1: https://dev.chromium.org/for-testers/providing-network-details
,
Feb 7 2017
,
Feb 20 2017
,
Feb 20 2017
Original reporter: Please file a new bug and refer to this bug in it if this issue is still happening. As Yutaka said, please attach a net-internals log if possible. It's also helpful if you attach some code for reproduction. Thanks |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by mc127...@gmail.com
, Feb 5 2017