New issue
Advanced search Search tips

Issue 663635 link

Starred by 3 users
Status: WontFix
Owner: ----
Closed: Nov 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Feature



Sign in to add a comment

Net-log the response headers on WebSocket handshake failure

Project Member Reported by ricea@chromium.org, Nov 9 2016 
For issues like 657791 it is troublesome that the response headers do not appear in the netlog. It makes it hard to diagnose the WebSocket handshake failures.

It would be good to log them, probably in WebSocketBasicHandshakeStream::ValidateResponse().
Project Member

Comment 1 by sheriffbot@chromium.org, Nov 9 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by ricea@chromium.org, Nov 10 2017

Status: WontFix (was: Untriaged)
Doesn't look like this will happen.
►

Sign in to add a comment