RESOLVED FIXED 214588
Fetch/XHR loads done by extensions should opt out of response sanitisation done in network process 
https://bugs.webkit.org/show_bug.cgi?id=214588
Summary Fetch/XHR loads done by extensions should opt out of response sanitisation do...
youenn fablet
Reported 2020-07-21 01:54:02 PDT
Fetch/XHR loads done by extensions should opt out of response sanitisation done in network process
Attachments
Patch (29.84 KB, patch)
2020-07-21 02:00 PDT, youenn fablet 		no flags
DetailsFormatted DiffDiff
Patch (16.02 KB, patch)
2020-07-21 03:59 PDT, youenn fablet 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
youenn fablet
Comment 1 2020-07-21 02:00:24 PDT
Created attachment 404804 [details] Patch
youenn fablet
Comment 2 2020-07-21 02:07:36 PDT
<rdar://problem/65060560>
youenn fablet
Comment 3 2020-07-21 03:59:28 PDT
Created attachment 404806 [details] Patch
Alex Christensen
Comment 4 2020-07-21 08:41:00 PDT
Comment on attachment 404806 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=404806&action=review > Source/WebKit/WebProcess/WebPage/WebPage.cpp:7148 > + // FIXME: We should probably have this mechanism done between UIProcess and NetworkProcess directly. I agree, but since this will only be done for a few long-lived pages, this is ok for now.
EWS
Comment 5 2020-07-21 11:13:23 PDT
Committed r264664: <https://trac.webkit.org/changeset/264664> All reviewed patches have been landed. Closing bug and clearing flags on attachment 404806 [details].
Note You need to log in before you can comment on or make changes to this bug.