-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changing of request headers (declarativeNetRequest) inside the side panel does not work #119
Comments
@Bhuvana-Priya , @sivsouvamMSFT 👋, 🙏. |
Hi @yankovichv , Thank you for reporting this. We are looking into this and will let you know as soon as we have an update. |
@yankovichv, can you share more details about where you're calling the declarativeNetRequest API from (static ruleset from manifest, background script, side panel surface, ...), whether you see any warning or error in the developer console when you make the call, and what the request domains are for which the header modification is not working? |
@abhishek-shanthkumar, we call the code from the service worker. We don't get any errors. The rules work fine in tabs but not in the side panel. |
@Bhuvana-Priya My code is free and Open-Source: Are there any updates? And what is the reason that your Microsoft web browser makes this different? |
Thanks, @yankovichv. It'll help if you can share a minimal extension with which the behaviour can be reproduced. If I understand it correctly, you make some network requests from your extension's side panel surface, and for those requests, the header modification rules don't apply (while they do for requests made from other surfaces like the popup and the service worker). Is that right? |
👋 |
@Bhuvana-Priya @abhishek-shanthkumar Is there any update about this important issue? As it is very important for my users. |
Sorry for the delay. I can repro the reported issue through the following steps:
Expected result: The site loads because the extension modifies the CSP headers. This is the behavior on Chrome. We're engaged with our security team to determine the best approach here. |
Hi @yankovichv, we apologize for the inconvenience. We are looking into this and will let you know as soon as we have an update. |
Why? Maybe I should specify some special parameters for the rule?
Example:
The text was updated successfully, but these errors were encountered: