NEW 162384
Web Inspector: network tab is not showing deep enough information 
https://bugs.webkit.org/show_bug.cgi?id=162384
Summary Web Inspector: network tab is not showing deep enough information
youenn fablet
Reported 2016-09-22 06:06:20 PDT
Web Inspector is typically presenting network requests and responses as exposed by XHR/fetch. It would be more appropriate to expose the requests and responses as done at the network level.
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2016-09-22 06:06:31 PDT
<rdar://problem/28425748>
youenn fablet
Comment 2 2016-09-22 06:10:47 PDT
I just tried running the following test: https://github.com/w3c/web-platform-tests/pull/3592/files Looking at firefox/chrome inspectors, we see that the second response is a 304 response at the network, that translates to a 200 response at JS level. The corresponding request also has specific cache headers, since it is a conditional request. Doing the same test on WebKit shows that the two responses are 200 and the second request is the same as the first one. Doing a quick wireshark test, the second request sent on the wire is a conditional request and the response is a 304 response. The low-level network information is much more interesting for debugging than the current exposed one. IIANM, the same principle applies for redirections: they are not exposed by web inspector while it is very useful debugging information.
youenn fablet
Comment 3 2016-09-22 06:11:55 PDT
See also related bug 160286: headers filtered out in a response do not get exposed by web inspector. This makes it harder to debug.
Note You need to log in before you can comment on or make changes to this bug.