WebSocket Messages are not listed in developer tools-> network tab
Categories
(DevTools :: Netmonitor, defect, P3)
Tracking
(Not tracked)
People
(Reporter: arshadrizwan96, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
11.22 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:93.0) Gecko/20100101 Firefox/93.0
Steps to reproduce:
opened an page having web socket connection.
Go to Developer tools -> network tab.
Click websocket request.
Check response of that request.
Actual results:
Response is empty.
Expected results:
Should have message sent and received the WS connection.
Comment 1•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'DevTools::Netmonitor' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Comment 2•4 years ago
|
||
Honza, can you share your test page and ask for more info? Thanks
Comment 4•4 years ago
|
||
Hello Angelina, help appreciated.
First step is to come up with a test case and reproduce the bug.
Perhaps you have a test case for this?
I tried on my local machine, but it seems to be working.
arshadrizwan96: Do you have a test case we could try to reproduce the problem on our machines?
Honza
(In reply to Jan Honza Odvarko [:Honza] (always need-info? me) from comment #4)
Hello, Honza!
Unfortunately, I don't have
I saw this test page in another bug - http://janodvarko.cz/test/websockets/, but it doesn't seem to be working
Comment 6•4 years ago
|
||
(In reply to Angelina from comment #5)
I saw this test page in another bug - http://janodvarko.cz/test/websockets/, but it doesn't seem to be working
Yes, it's based on ws://echo.websocket.org/, which is no longer available
| Reporter | ||
Comment 7•4 years ago
|
||
(In reply to Jan Honza Odvarko [:Honza] (always need-info? me) from comment #4)
Hello Angelina, help appreciated.
First step is to come up with a test case and reproduce the bug.
Perhaps you have a test case for this?I tried on my local machine, but it seems to be working.
arshadrizwan96: Do you have a test case we could try to reproduce the problem on our machines?
Honza
Hi Honza,
I have checked with some other page's websocket, which is working fine. SO I'm checking the difference b/w these two websocket request. Also, the websocket messages for the same website(where the messages are hidden in firefox) are able to view in chrome's devtool.
Comment 8•4 years ago
|
||
(In reply to arshadrizwan96 from comment #7)
I have checked with some other page's websocket, which is working fine. SO I'm checking the difference b/w these two websocket request. Also, the websocket messages for the same website(where the messages are hidden in firefox) are able to view in chrome's devtool.
Perfect, thank you!
In order to fix this, we need clean STRs to be able to see the problem on our machines.
Please keep us updated.
Comment 9•4 years ago
|
||
The severity field is not set for this bug.
:Honza, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•4 years ago
|
Updated•4 years ago
|
Comment 10•4 years ago
|
||
@arshadrizwan96, any progress with the test case?
Comment 11•3 years ago
|
||
Clear a needinfo that is pending on an inactive user.
Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.
For more information, please visit auto_nag documentation.
Comment 12•3 years ago
|
||
This is still an issue with 110.0.1
To reproduce locally using a docker-based websocket echo server:
- docker run --detach -p 10000:8080 jmalloc/echo-server
- navigate to http://localhost:10000/.ws
- the page will send websocket messages every second
- go to developer console -> Network
- nothing logged there
Comment 13•2 years ago
|
||
(In reply to starbrk from comment #12)
This is still an issue with 110.0.1
To reproduce locally using a docker-based websocket echo server:
- docker run --detach -p 10000:8080 jmalloc/echo-server
- navigate to http://localhost:10000/.ws
- the page will send websocket messages every second
- go to developer console -> Network
- nothing logged there
I've experienced the same issue on Firefox 117.0. Not sure if this is related but I also enabled the "Do not clear logs" option in the network tab. Would be cool to at lease have a work around for this since it's quite cumbersome to debug like this...
Comment 16•2 years ago
|
||
On firefox 117.0.1 (64-bit) from Ubuntu via the Snap install. Websocket from the network tab of the devtools will not list the message unless the setting "persist logs" is enabled.
Comment 17•2 years ago
•
|
||
For me in 121.0b1, the the "Messages" Tab is not visible in the right-side panel of the network inspector when clicking any websocket request that was upgraded via "101 Switching Protocols". Enabling "Persist Logs" does not show the tab either. What are the conditions for this tab to show?
Comment 18•1 year ago
|
||
(In reply to silverwind from comment #17)
For me in 121.0b1, the the "Messages" Tab is not visible in the right-side panel of the network inspector when clicking any websocket request that was upgraded via "101 Switching Protocols". Enabling "Persist Logs" does not show the tab either. What are the conditions for this tab to show?
It is in a different tab, called "Response".
By reading and seeing the screenshots in this article I was expecting to have a "Messages" tab:
https://hacks.mozilla.org/2019/10/firefoxs-new-websocket-inspector/
If the article can be edited with some notes stating the messages are (now) in the "Response" tab, that would be appreciated.
Comment 19•11 months ago
|
||
Can't use the provided STRs, I will leave open for now, but if anyone experiences this on a publicly available test page, can you please share a link here?
Updated•11 months ago
|
Description
•