RESOLVED DUPLICATE of bug 253696263818
declarativeNetRequest modifyHeaders for response should be allowed 
https://bugs.webkit.org/show_bug.cgi?id=263818
Summary declarativeNetRequest modifyHeaders for response should be allowed
Guilherme Rizzo
Reported 2023-10-27 19:09:50 PDT
I'm trying to build a "Responsive Viewer" extension for Safari with a Safari Web Extension. The extension loads a page into an iframe so that the user can resize and check how the page is responsive. Some websites won't load in iframes. In Chrome, I can use declarativeNetRequest to modify the response headers and remove the "frame-options" header that blocks the page from being loaded into an iframe. Loading the page into an iframe is the only way a "Responsive Viewer" extension could work. The extension already has all the permissions it needs from the user, and declarativeNetRequest is the safest way. Please let extensions modify headers from the response as well.
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2023-10-27 19:09:59 PDT
<rdar://problem/117613989>
Karl Dubost
Comment 2 2023-11-06 18:59:56 PST
Thanks for the bug, probably a duplicate of Bug 246493 *** This bug has been marked as a duplicate of bug 246493 ***
Guilherme Rizzo
Comment 3 2023-11-06 19:02:16 PST
declarativeNetRequest is supported and works. Just some of its features are missing, like modifyHeaders for response. I didn't know that was planned to be shipped :D
Karl Dubost
Comment 4 2023-11-06 19:49:21 PST
Ah then let's change the relation. *** This bug has been marked as a duplicate of bug 253696 ***
Note You need to log in before you can comment on or make changes to this bug.