Bug 1888102: Update tests within netwerk/ to work with https-first enabled, r=kershaw,necko-reviewers

Differential Revision: https://phabricator.services.mozilla.com/D205821
This commit is contained in:
Christoph Kerschbaumer 2024-03-27 14:11:15 +00:00
parent 4d3b76cb63
commit b4860b5481
3 changed files with 17 additions and 1 deletions

View file

@ -4,6 +4,14 @@
*/
"use strict";
// performing http and https testing within this file,
// and we do not want https-first to interfere with that test
Services.prefs.setBoolPref("dom.security.https_first", false);
registerCleanupFunction(function () {
Services.prefs.clearUserPref("dom.security.https_first");
});
const {
HTTPS_EXAMPLE_ORG,
HTTPS_EXAMPLE_COM,

View file

@ -5,6 +5,14 @@
"use strict";
// performing http and https testing within this file,
// and we do not want https-first to interfere with that test
Services.prefs.setBoolPref("dom.security.https_first", false);
registerCleanupFunction(function () {
Services.prefs.clearUserPref("dom.security.https_first");
});
const {
HTTPS_EXAMPLE_ORG,
HTTPS_EXAMPLE_COM,

View file

@ -239,6 +239,7 @@ add_task(async () => {
await testTrailingDotCookie("http://foo.com/", "foo.com");
cm.removeAll();
Services.prefs.clearUserPref("dom.security.https_first");
});
function getCookieCount() {
@ -285,5 +286,4 @@ async function testTrailingDotCookie(uriString, domain) {
Assert.equal(cm.countCookiesFromHost(domain), 0);
Assert.equal(cm.countCookiesFromHost(domain + "."), 0);
cm.removeAll();
Services.prefs.clearUserPref("dom.security.https_first");
}