adjust more tests to work with https-first mode
Categories
(Core :: DOM: Security, task, P3)
Tracking
()
People
(Reporter: freddy, Assigned: freddy)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-active])
Attachments
(2 files, 1 obsolete file)
++ This bug was filed as a friend of bug 1743626 ++
We need to repair some tests so they don't break due to http->https upgrades e.g., when sites suddenly become same/cross-origin unexpectedly.
Assignee | ||
Comment 1•3 years ago
|
||
Assignee | ||
Comment 2•3 years ago
|
||
Let's leave this bug open in case there are more tests that need annotating.
Comment 4•3 years ago
|
||
bugherder |
Updated•3 years ago
|
Assignee | ||
Comment 5•3 years ago
|
||
Comment 7•3 years ago
|
||
bugherder |
Comment 8•3 years ago
|
||
bugherder |
Assignee | ||
Comment 9•3 years ago
|
||
This adjust some recently added/modified tests to compyl with
https-first enabled.
-
browser_ext_webRequest_error_after_stopped_or_closed.js
The test opens a new tab for top navigation and expects it to stay HTTP.
The test was modified to open-as HTTPS and expect as HTTPS. -
browser_net_har_copy_all_as_har.js
The test performs a request to an HTTP resource.
The test was modified to open-as HTTPS and expect as HTTPS, furthermore
the test had more expectation about the outgoing request and its
response, e..g, the amount of headers. Those things had to be modified,
as a secure connection also inludes Sec-Fetch-* headers and
Upgrade-Insecure-Requests -
browser_download_idn_blocklist.js
The server runs its own webserver, which was non-trivial to switch to
HTTPS, so we are now running this test with https-first mode always
disabled.
Updated•3 years ago
|
Comment 10•3 years ago
|
||
The leave-open keyword is there and there is no activity for 6 months.
:freddy, maybe it's time to close this bug?
For more information, please visit auto_nag documentation.
Assignee | ||
Updated•3 years ago
|
Description
•