Summary: | It should be easy for developers to know which response headers are filtered out by fetch algorithm | ||
---|---|---|---|
Product: | WebKit | Reporter: | youenn fablet <youennf> |
Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW --- | ||
Severity: | Normal | CC: | achristensen, ap, bburg, joepeck, jonlee, m.goleb+bugzilla, sidneybeekhoven, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
See Also: |
https://bugs.webkit.org/show_bug.cgi?id=158565 https://bugs.webkit.org/show_bug.cgi?id=162384 |
Description
youenn fablet
2016-07-28 00:52:12 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. |