Bug 1915176 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Follow-up to Bug 1904238. With the changes from that patch, we can now clean up [this](https://searchfox.org/mozilla-central/rev/ece43b04e7baa4680dac46a06d5ad42b27b124f4/dom/security/nsHTTPSOnlyUtils.cpp#751-766) section greatly. Due to Bug 1904238 clearing the HTTPS-Only flag on every redirect, we should no longer need to clear it in the code linked above. This also means we can get rid of `HTTPS_FIRST_EXEMPT_NEXT_LOAD`, which currently is a bit confusing.  It just exists to "survive" our current clearing of the exemption flag, as there are some cases where we know that the load should be exempt from HTTPS-First (for example loading http history entries) before we reach the code clearing the exemption status.
Follow-up to Bug 1904238. With the changes from that patch, we can now clean up [this](https://searchfox.org/mozilla-central/rev/ece43b04e7baa4680dac46a06d5ad42b27b124f4/dom/security/nsHTTPSOnlyUtils.cpp#751-766) section. Due to Bug 1904238 clearing the HTTPS-Only flag on every redirect, we should no longer need to clear it in the code linked above. This also means we can get rid of `HTTPS_FIRST_EXEMPT_NEXT_LOAD`, which currently is a bit confusing.  It just exists to "survive" our current clearing of the exemption flag, as there are some cases where we know that the load should be exempt from HTTPS-First (for example loading http history entries) before we reach the code clearing the exemption status.

Back to Bug 1915176 Comment 0