<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Web Inspector: network tab is not showing deep enough information"
href="https://bugs.webkit.org/show_bug.cgi?id=162384#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Web Inspector: network tab is not showing deep enough information"
href="https://bugs.webkit.org/show_bug.cgi?id=162384">bug 162384</a>
from <span class="vcard"><a class="email" href="mailto:youennf@gmail.com" title="youenn fablet <youennf@gmail.com>"> <span class="fn">youenn fablet</span></a>
</span></b>
<pre>I just tried running the following test: <a href="https://github.com/w3c/web-platform-tests/pull/3592/files">https://github.com/w3c/web-platform-tests/pull/3592/files</a>
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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>