I’ve been using “overrideHost * [SOME_HOST]” successfully with HTTP pages, but when I try the same thing on an HTTPS page (I’ve tried with Chrome so far) it doesn’t seem to work.
Is this expected?
I think it might be a Chrome-specific bug that I need to look into. For the other browsers I have access to the raw socket streams, even for encrypted connections. For Chrome that all needs to be done in a separate code path by the extension and it’s possible that Chrome changed behavior and broke something.