Bug 160286 - It should be easy for developers to know which response headers are filtered out by fetch algorithm
Summary: It should be easy for developers to know which response headers are filtered ...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2016-07-28 00:52 PDT by youenn fablet
Modified: 2020-09-17 00:13 PDT (History)
8 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description youenn fablet 2016-07-28 00:52:12 PDT 
This applies to fetch API at least.
Based on bug 158565, this may be applicable to XHR as well.
Comment 1 youenn fablet 2016-07-28 00:54:57 PDT 
XHR somehow gives this information by adding a debug message on the console log.
This is removed in bug 158565 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.
Comment 2 Radar WebKit Bug Importer 2016-11-01 17:05:01 PDT 
<rdar://problem/29055617>