Closed
Bug 1901017
Opened 4 months ago
Closed 1 month ago
Write automated testcase for schemeless upgrade-downgrade
Categories
(Core :: DOM: Security, task, P2)
Core
DOM: Security
Tracking
()
RESOLVED
DUPLICATE
of bug 1883954
People
(Reporter: ckerschb, Assigned: maltejur)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-active])
We have a testcase https-first/browser_schemeless.js which only tests that the schemeless input gets upgraded to https, though I think we should also have one that ensure that the downgrade is happening in case it can not be upgraded.
|
Reporter | |
Updated•4 months ago
|
Blocks: schemeless-https-first, https-first-mode
|
||
Comment 1•4 months ago
|
||
Malte: do we already have a testcase for this, or can you adapt an existing one fairly painlessly?
Flags: needinfo?(mjurgens)
|
Assignee | |
Comment 2•4 months ago
|
||
dom/security/test/https-first/browser_schemeless.js should be easy to adapt. I'll work on doing that once I have some time.
Assignee: nobody → mjurgens
Status: NEW → ASSIGNED
Flags: needinfo?(mjurgens)
|
|
||
Updated•4 months ago
|
Severity: -- → N/A
Whiteboard: [domsecurity-active]
|
||
Updated•2 months ago
|
Priority: -- → P2
|
|
Assignee | |
Comment 3•1 month ago
|
||
This should already be covered by the tests introduced recently with the HTTPS upgrade telemetry in Bug 1883954: https://searchfox.org/mozilla-central/rev/490a1df802d8872f996f8ef4093d54e3c854c8f9/dom/security/test/https-first/browser_https_telemetry.js#473-488
You need to log in
before you can comment on or make changes to this bug.
Description
•