Bug 263818

Summary:	declarativeNetRequest modifyHeaders for response should be allowed
Product:	WebKit	Reporter:	Guilherme Rizzo <guivr2011>
Component:	WebKit Extensions	Assignee:	Nobody <webkit-unassigned>
Status:	RESOLVED DUPLICATE
Severity:	Normal	CC:	karlcow, timothy, webkit-bug-importer
Priority:	P2	Keywords:	InRadar
Version:	Safari 16
Hardware:	Mac (Apple Silicon)
OS:	macOS 13

Description Guilherme Rizzo 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.

Comment 1 Radar WebKit Bug Importer 2023-10-27 19:09:59 PDT

<rdar://problem/117613989>

Comment 2 Karl Dubost 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 ***

Comment 3 Guilherme Rizzo 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

Comment 4 Karl Dubost 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 ***