Closed
Bug 1741590
Opened 3 years ago
Closed 3 years ago
Update more tests within toolkit/components/extensions/test to work with https-first enabled
Categories
(Core :: DOM: Security, task, P3)
Core
DOM: Security
Tracking
()
RESOLVED
FIXED
96 Branch
| Tracking | Status | |
|---|---|---|
| firefox96 | --- | fixed |
People
(Reporter: ckerschb, Assigned: robwu)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-active])
Attachments
(2 files, 1 obsolete file)
No description provided.
|
Reporter | |
Comment 1•3 years ago
|
||
|
||
Updated•3 years ago
|
Assignee: nobody → ckerschb
Status: NEW → ASSIGNED
|
Assignee | |
Comment 2•3 years ago
|
||
Taking over as requested by Christoph, since I have more domain knowledge on these specific tests.
Assignee: ckerschb → rob
|
|
Assignee | |
Comment 3•3 years ago
|
||
Some fixups are trivial; mostly just ensuring that https is opened and
matched by the content script.
In test_ext_browsingData_indexedDB.html, the fix was more involved:
http://mochi.test:8888 cannot use https because there is no https
server at mochi.test, port 8888.
So in that case I used example.org as a new/unique origin instead,
which is one of the available origin aliases for the local http(s)
server, listed at build/pgo/server-locations.txt.
|
|
Assignee | |
Comment 4•3 years ago
|
||
|
|
||
Updated•3 years ago
|
Attachment #9251113 -
Attachment is obsolete: true
Pushed by rob@robwu.nl:
https://hg.mozilla.org/integration/autoland/rev/1f1f3d346cc9
Update remaining tests in toolkit/components/extensions/test/mochitest/ to work with https-first enabled r=mixedpuppy
https://hg.mozilla.org/integration/autoland/rev/66396b50cbab
Disable https_first in toolkit/components/extensions/test/xpcshell/ r=ckerschb
|
||
Comment 6•3 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/1f1f3d346cc9
https://hg.mozilla.org/mozilla-central/rev/66396b50cbab
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox96:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 96 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•