WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
NEW
160286
It should be easy for developers to know which response headers are filtered out by fetch algorithm
https://bugs.webkit.org/show_bug.cgi?id=160286
Summary
It should be easy for developers to know which response headers are filtered ...
youenn fablet
Reported
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.
Attachments
Add attachment
proposed patch, testcase, etc.
youenn fablet
Comment 1
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.
Radar WebKit Bug Importer
Comment 2
2016-11-01 17:05:01 PDT
<
rdar://problem/29055617
>
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug