Why does Chrome developer console dos not show network request's detail? I expect there to be (and it was) all details about network request related to the loaded page.
Related
I was trying to understand how https://webk.telegram.org works, so I opened chrome dev tools and went to inspect the network traffic.
I was surprised to see that when I send a message in telegram I don't see any xhr nor websocket traffic in chrome dev tools.
Any idea through which channel the traffic is going ? Why is it not intercepted by chrome network inspector (and can this be fixed)?
I am trying to build a PWA (Progressive Web App) but the Chrome devtools console is warning that it is blocking my css and icon file.
Request was blocked by DevTools: "https://example.com/styles/style.css".
I cannot find any information about this happening automatically and, to my knowledge, should only happen if the user has manually requested to block a script. Chrome does not offer any other information about the warnings other than being blocked.
This error means the domain or URL has been blocked in the devtools. Most of the time, it's just because the developer blocked the request without paying attention.
To unblock it, just follow these steps:
Open your devtools
Go to the network tab
Right-click on the request that blocked
Then click Unblock <request-url>
I currently am using Chrome 79 with the flags enabled to emulate the upcoming feature in Chrome 80
chrome://flags/#same-site-by-default-cookies
chrome://flags/#cookies-without-same-site-must-be-secure
When I visit a site with my Developer Tools open and review the console logs, all it says is that it blocked a cookie, with no idication WHAT cookie it blocked.
How do I determine what cookie was blocked?
Try it in Chrome Canary. You still have to manually enable the flags for some reason (despite Canary being Chrome 81 at this point), but you have the option to only show blocked cookies, which provide you with a lot more information.
Why I cannot see network activity in WhatsApp Web? I mean in developer tools (F12), in the Network tab. I tried with both Firefox and Google Chrome.
In Firefox navigate to web.whatsapp.com. Open developer tools (F12). Go to network tab. Select WS. Refresh the web page. Now you can see the web socket logs.
You won't see network traffic if you open developer tools after initial WS is send.
I can use the Network tab in the Google Chrome Web Inspector to debug the network traffic (AJAX requests, etc.). I can check what data is transferred easily. But Websocket connections only show as
Request URL:ws://localhost/...
Request Method:GET
Status Code:101 Switching Protocols
...
and I can't see the transferred data. Is there any build in feature in Google Chrome to inspect the transferred data? Or do I need to use Wireshark?
PS: I'm using the latest stable version (16.0.912.75). If a newer version (beta/dev) has this features, it would be nice.
Chrome and Chromium now have WebSocket message frame inspection. Here are the steps to test it quickly:
Navigate to the WebSocket Echo demo, hosted on the websocket.org site.
Turn on the Chrome Developer Tools.
Click Network, enable filter (3rd icon from the left on the top of Dev Tools) to filter the traffic shown by the Developer Tools, and click WebSockets.
In the Echo demo, click Connect. On the Headers tab in Google Dev Tool you can inspect the WebSocket handshake.
Click the Send button in the Echo demo.
To see the WebSocket frames in Chrome Developer Tools, under Name, click the entry representing your WebSocket connection. This refreshes the main panel on the right and makes the WebSocket Frames tab show up with the actual WebSocket message content.
I also posted the steps with screen shots and video.
After some more research I found a duplicate question here: Debugging WebSocket in Google Chrome
Chrome does't support viewing the traffic in the current stable version. I need to use Wireshark.
Another Idea, for simple web socket testing and lightweight, use Chrome plugin "Simple Web-socket. I wanted to check only if the connection can be establish or not. Following Chrome plugin "Simple Web-socket (link : https://chrome.google.com/webstore/detail/simple-websocket-client/pfdhoblngboilpfeibdedpjgfnlcodoo?hl=en)" work like charm. See image.
https://lh3.googleusercontent.com/bEHoKg3ijfjaE8-RWTONDBZolc3tP2mLbyWanolCfLmpTHUyYPMSD5I4hKBfi81D2hVpVH_BfQ=w640-h400-e365