CORS Policy for Addon request

[barraiser (admin@barraiser.com)]

We are calling multiple APIs in our addon to enable lot of features in our addon. But our application server is rejecting the request due to CORS error.

We tried whitelisting the origin which in generated in the addon but it seems the origin changes on every installation on any machine.

I can not all all domains to call my API. Basically I can not allow “*” as CORS policy on application server.

Please help us with the suggestion on

1. How to make the addon origin as some static UUID value.
2. How to configure application server CORS policy to allow only my addon to make API calls?

[juraj.masiar]

Similar issue has been recently discussed here:

How to keep the same internal UUID by installing a Firefox add-on in unlisted mode?

Good morning, I am developing a browser add-on for Firefox. I would like to ask a question. Is it possible to publish the add-on in an unlisted way, but making sure that when it is installed in the browser it always maintains the same internal UUID (which does not correspond to the add-on ID)? If it is not possible to do this by publishing it unlisted, would it be possible to do so by publishing it in your store in a listed way? I await your kind reply Thank you, best regards

I have several addons that communicate with my server and I’ve never had issues with CORS, that is when the request was send from background script or from the extension page (so not a content script), and while my addon had the host permission for my server domain name.

And this should work without disabling CORS on your server, and without whitelisting your addon UUID.

[Patpa99 (Paolo)]

Yes…but, as you will see from the problem discussed above, my add-on also had host permission for my server’s domain name and I was sending requests from the background script.
Unfortunately we have not found a solution (I’m still open to any kind of help or advice)

[juraj.masiar]

Could you post here the screenshot of the headers of the problematic request, in the Network tab?
Like this:

Also, any chance something is modifying your request/response headers?

[jessica1 (mfaisal.ati@gmail.com)]

Confirm that the background script is properly configured and running in your add-on. Look for any console errors in the background script by checking the browser’s developer tools.

[jessica1 (mfaisal.ati@gmail.com)]

This post was flagged by the community and is temporarily hidden.