Closed
Bug 1736562
Opened 3 years ago
Closed 7 days ago
Test that slow nonstandard port sites don't get timeout
Categories
(Core :: DOM: Security, task, P3)
Core
DOM: Security
Tracking
()
RESOLVED
FIXED
132 Branch
Tracking | Status | |
---|---|---|
firefox132 | --- | fixed |
People
(Reporter: t.yavor, Assigned: maltejur)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-active])
Attachments
(1 file)
Test that for (slow) sites with non standard ports https-first is not running into a timeout error.
Related is that test to the bug 1731971: https://bugzilla.mozilla.org/show_bug.cgi?id=1731971
Reporter | ||
Updated•3 years ago
|
Assignee: nobody → lyavor
Reporter | ||
Comment 1•3 years ago
|
||
Updated•3 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P3
Whiteboard: [domsecurity-active]
Updated•1 year ago
|
Assignee: t.yavor → nobody
Status: ASSIGNED → NEW
Updated•1 year ago
|
Severity: -- → S4
Comment 2•1 month ago
|
||
We no longer want to upgrade non-standard ports w/ HTTPS-First Mode. Malte, can you take a look if there are bugs / complications in how First & Only interact with each other?
Status: NEW → RESOLVED
Closed: 1 month ago
Flags: needinfo?(maltejur)
Resolution: --- → FIXED
Updated•23 days ago
|
Assignee: nobody → maltejur
Assignee | ||
Comment 3•23 days ago
|
||
This bug only seems to be about writing a testcase for the already fixed behavior (despite not acting on non-standard ports, HTTPS-First would timeout requests on them after 3s). Tomer already started work on such a testcase, and as I think it is as good as finished, I'll work on getting it landed.
Status: RESOLVED → REOPENED
Flags: needinfo?(maltejur)
Resolution: FIXED → ---
Pushed by mjurgens@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c725ae935814
Test that slow nonstandard port sites don't get timeout. r=freddyb
Comment 5•7 days ago
|
||
bugherder |
Status: REOPENED → RESOLVED
Closed: 1 month ago → 7 days ago
status-firefox132:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 132 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•