Closed fmarier closed 6 years ago
WebExtensions do not (yet?) offer APIs to intercept and modify the typed URL (or to distinguish between typing http://example.com
, https://example.com
or example.com
).
I think that the closest approximation is to unconditionally use https for all top-level requests that are not initiated by a web page (and offer the ability to use the http version if the https site cannot be reached).
I just filed https://bugzilla.mozilla.org/show_bug.cgi?id=1370388 to propose the API you suggested above.
@fmarier By your experiences, what is ETA for the API to be implemented?
The priority has been set to P5, which means: "we're not going to work on it, but patches welcome."
The README says that the Chrome API for extensions is not powerful enough to enable https-by-default. Have you looked at the Web Extensions API?