My question is about sending AJAX (HTTPS) requests to a server that I own from the background page of my Chrome extension. I have found that without adjusting browser settings, it is difficult to send such requests to an unsigned/self-signed server. I am curious if Chrome extensions have different privileges in this regard, as requiring users to change their browser settings is not ideal.
In monitoring my own extension, I have noticed that all HTTPS requests sent by my background page appear to be 'canceled' according to the dev console.
Are there any solutions to this issue other than obtaining a signed certificate or resorting to workaround techniques like simulating a secure connection with HTTP?