网站发出的网络请求未显示在 Chrome DevTools 或 Fiddler 中
Network request made by a website is not showing in Chrome DevTools nor Fiddler
这种情况不容易重现，因为website需要通过Steam登录。
该网页显示了可以购买的项目列表。每当列出新项目时，它将出现在项目列表的顶部。但是，在检查 Chrome DevTools 和 Fiddler 时，我找不到包含新列出的项目数据的请求。事实上，根本没有任何请求。
我没有在 Chrome DevTools 中使用任何过滤器。
此网页如何从服务器检索数据，为什么 Chrome 和 Fiddler 不接受它？
本题包含答案：
jvda:
This is a common source of conufsion when debugging networking requests done from the web. Normally, developers look at these network requests from top down and assume that the lowest one is the most recent request made - therefore assuming that the request must be at the bottom. For 'plain' HTTP this is correct. However, many apps that want to show data in real-time, use WebSockets to communicate with an API.
The same thing happens in the Web-version of Whatsapp. Only assets like the actual JavaScript-app, icons etc are loaded using plain HTTP. Then, a WebSocket is opened through which messages are exchanged for example.
我认为这个问题无关紧要，但我想事实并非如此。数据通过WebSockets交换
这种情况不容易重现，因为website需要通过Steam登录。
该网页显示了可以购买的项目列表。每当列出新项目时，它将出现在项目列表的顶部。但是，在检查 Chrome DevTools 和 Fiddler 时，我找不到包含新列出的项目数据的请求。事实上，根本没有任何请求。
我没有在 Chrome DevTools 中使用任何过滤器。
此网页如何从服务器检索数据，为什么 Chrome 和 Fiddler 不接受它？
本题包含答案：
jvda:
This is a common source of conufsion when debugging networking requests done from the web. Normally, developers look at these network requests from top down and assume that the lowest one is the most recent request made - therefore assuming that the request must be at the bottom. For 'plain' HTTP this is correct. However, many apps that want to show data in real-time, use WebSockets to communicate with an API.
The same thing happens in the Web-version of Whatsapp. Only assets like the actual JavaScript-app, icons etc are loaded using plain HTTP. Then, a WebSocket is opened through which messages are exchanged for example.
我认为这个问题无关紧要，但我想事实并非如此。数据通过WebSockets交换