New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 757758 link

Starred by 3 users
Status: WontFix
Owner:
█ allada@chromium.org
Last visit > 30 days ago
Closed: Dec 2017
Cc:
ajha@chromium.org
█ msrchandra@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Feature



Sign in to add a comment

Show websocket frame header

Reported by jeromin....@gmail.com, Aug 22 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3188.4 Safari/537.36

Steps to reproduce the problem:
Every WS frame has own headers.

What is the expected behavior?
It would be nice if the header of every frame could be shown.

What went wrong?
Right now only the HTTP header for the WS setup are shown.

Did this work before? No 

Chrome version: 62.0.3188.4  Channel: dev
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:

Comment 1 by msrchandra@chromium.org, Aug 23 2017

Cc: msrchandra@chromium.org
Labels: Needs-Feedback
@jeromin.holger -- Thank You for the report.
Could you please provide us any screen shot or screen cast for the issue which would help us triage the issue further.
Thanks in Advance.

Comment 2 by jeromin....@gmail.com, Aug 23 2017 

This is no bug but a feature request for the devTools.
I have attached a screenshot what wireshark displays for a websocket frame.
Websocket in Wireshark.png
15.7 KB View Download
Project Member

Comment 3 by sheriffbot@chromium.org, Aug 23 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "msrchandra@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Comment 4 by ajha@chromium.org, Aug 24 2017

Cc: ajha@chromium.org
Labels: -Type-Bug Needs-Triage-M62 M-62 OS-Linux OS-Mac Type-Feature
Status: Untriaged (was: Unconfirmed)
Marking this as Untriaged and as Feature request for more inputs by the respective team.

Comment 5 by pfeldman@chromium.org, Aug 28 2017

Owner: allada@chromium.org
Status: Assigned (was: Untriaged)

Comment 6 by pfeldman@chromium.org, Dec 13 2017

Status: WontFix (was: Assigned)
Closing due to lack of priority / resources.
►

Sign in to add a comment