Open
Bug 1470501
Opened 6 years ago
Updated 2 years ago
invalid https certificates result in a "corrupted content" warning rather than something useful
Categories
(Core :: DOM: Core & HTML, defect, P3)
Core
DOM: Core & HTML
Tracking
()
NEW
People
(Reporter: froydnj, Unassigned)
Details
STR (may not work perfectly due to caching, or may require system time hacking to get things into cache first? site may also fix their certificate before we fix this bug...):
1. Visit https://forum.stimhack.com/.
ER:
Site comes up.
AR:
A page saying:
Corrupted Content Error
The site at https://forum.stimhack.com/ has experienced a network protocol violation that cannot be repaired.
The page you are trying to view cannot be shown because an error in the data transmission was detected.
The circumstances are kind of similar to bug 1310893; you can see an error message in the console:
"Failed to load ‘https://forum.stimhack.com/’. A ServiceWorker passed a promise to FetchEvent.respondWith() that rejected with ‘TypeError: NetworkError when attempting to fetch resource.’."
presumably because the site's HTTPS certificate has expired.
Force-refreshing the page brings up the "Your connection is not secure" page, which is at least actionable.
It would be nice if the service worker error could be propagated up the stack in such a way as to present the "Your connection is not secure" page, rather than a "corrupted content" page, which is inaccurate.
Updated•6 years ago
|
Priority: -- → P3
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•