You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In extension I am maintaining it's required to perform multiple HTTP requests. In most cases when request fails everything goes smoothly, but for some class of errors both XHR and Fetch break and start throwing Content Security Policy: The page’s settings blocked the loading of a resource at [URI] (“default-src moz-extension://[extension id]”). errors for every single request attempted, creating new XHR objects doesn't help, only reloading the extension unlocks the ability to perform requests.
To Reproduce
As I'm not able to pinpoint class of errors that cause this issue I can't provide reliable way to reproduce
Expected behavior
Failed request shouldn't make other requests fail
Additional context
thanks to mozregression I pinpointed 2017-08-09 to be the first good official build, earlier ones also had this issue.
The text was updated successfully, but these errors were encountered:
Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.96. Please mark this comment with 👍 or 👎 to give our bot feedback!
Describe the bug
In extension I am maintaining it's required to perform multiple HTTP requests. In most cases when request fails everything goes smoothly, but for some class of errors both XHR and Fetch break and start throwing
Content Security Policy: The page’s settings blocked the loading of a resource at [URI] (“default-src moz-extension://[extension id]”).
errors for every single request attempted, creating new XHR objects doesn't help, only reloading the extension unlocks the ability to perform requests.To Reproduce
As I'm not able to pinpoint class of errors that cause this issue I can't provide reliable way to reproduce
Expected behavior
Failed request shouldn't make other requests fail
Additional context
thanks to mozregression I pinpointed
2017-08-09
to be the first good official build, earlier ones also had this issue.The text was updated successfully, but these errors were encountered: