Fetch request in content script problems

Add-ons Development
1

Two problems:

  1. can’t debug the request
    • not in the network tab (developer tools) of the page,
    • not in the inspect extension toolbox

I needed the referrer policy extension to debug the request and find out the second problem:

  1. fetch request in content script doesn’t add the origin header, I consider that a bug.
1 Like
4

Thanks, but maybe I was not completely clear. It’s not about referrer policy.

I have another extension that injects a content-script and in that content script a fetch request is made.

I can’t debug that request like described.

I needed the referrer policy extension for that.

2 Likes
5

If a request was blocked, the

request list

shows the reason, such as an add-on, CSP, CORS, or Enhanced Tracking Protection. ([bug 1555057]

(https://bugzilla.mozilla.org/show_bug.cgi?id=1555057), [bug 1445637]

(https://bugzilla.mozilla.org/show_bug.cgi?id=1445637), [bug 1556451]

(https://bugzilla.mozilla.org/show_bug.cgi?id=1556451))

Maybe we such a case here?

6

@anon83004023

No, it doesn’t show up in the network tab (Network request list), doesn’t matter if it’s loading or not.