<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - It should be easy for developers to know which response headers are filtered out by fetch algorithm"
href="https://bugs.webkit.org/show_bug.cgi?id=160286#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - It should be easy for developers to know which response headers are filtered out by fetch algorithm"
href="https://bugs.webkit.org/show_bug.cgi?id=160286">bug 160286</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>XHR somehow gives this information by adding a debug message on the console log.
This is removed in <a class="bz_bug_link
bz_status_NEW "
title="NEW - Compute fetch response type in case of cross-origin requests"
href="show_bug.cgi?id=158565">bug 158565</a> as filtering is done at DocumentThreadableLoader level.
We could add a message on the console log detailing which headers are filtered out.
The inspector could also be enhanced to display all response headers and which are visible/not visible.</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>