Avoid timeouts within HTTPS-Only Mode by sending background http request
Categories
(Core :: DOM: Security, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox81 | --- | fixed |
People
(Reporter: arthur, Assigned: ckerschb)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [domsecurity-active][tor-P1])
Attachments
(3 files)
Steps to reproduce:
- Set dom.security.https_only_mode to true
- Enter "people.cn" in the URL bar
Actual results:
The browser waits for 90 seconds and then shows the "Secure Connection Unavailable" error page, with a "Timed Out" status bar message. During this time, the user can get the impression that the website isn't working at all.
Desired results:
The browser rapidly shows the "Secure Connection Unavailable" error page. If that isn't possible, then a non-blocking notification bar or doorhanger that gives the user an option to "Accept the Risk and Continue to Site" before waiting the full 90 seconds.
Comment 1•5 years ago
|
||
Hi Arthur,
thanks for opening this bug! I'll look into fixing this ^^
Reporter | ||
Comment 2•5 years ago
|
||
Thanks, Julian!
Another website with the same behavior:
moonlander.seb.ly
Comment 3•5 years ago
|
||
The severity field is not set for this bug.
:ckerschb, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee | ||
Updated•5 years ago
|
Reporter | ||
Comment 4•5 years ago
|
||
I assume websites like this are not responding at all to HTTPS requests. One idea for fixing this failure mode might be: if no response is received from an upgraded HTTPS connection attempt after 500 ms (or similar timeout), send an HTTP request in the background. If we then receive an HTTP response before any HTTPS response, show the HTTPS Only Mode error page.
Reporter | ||
Comment 5•5 years ago
|
||
Another site:
http://speedofanimals.com
Reporter | ||
Comment 6•5 years ago
|
||
Another site:
http://randomwalker.info
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 8•5 years ago
|
||
...page instead. r=dragana
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 9•5 years ago
|
||
Comment 10•5 years ago
|
||
Comment 11•5 years ago
|
||
Backed out for perma failures.
Log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=312621185&repo=autoland&lineNumber=14620
Backout: https://hg.mozilla.org/integration/autoland/rev/3356b4e765e7598963fe0a62d80d889c221eaae9
Assignee | ||
Comment 12•5 years ago
|
||
(In reply to Razvan Maries from comment #11)
Backed out for perma failures.
Huh, is that really a perma failure? I can't imagine because it works locally on mac and linux. Currently I can't reproduce the problem. I'll see what I can do here.
Updated•5 years ago
|
Comment 13•5 years ago
|
||
Comment 14•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/d31509a36f35
https://hg.mozilla.org/mozilla-central/rev/863cf62af994
Reporter | ||
Updated•5 years ago
|
Description
•