Firefox/Projects/Network Error Pages
Jump to navigation
Jump to search
Overview
Sprint lead: curtis
Sprinters: johnath, boriss
- Description
- More useful/helpful set of network error pages that offer tools helping users get to a useful end point via search, analysis of Places DB, or automatic redirects/reloads.
Steps
- Identify the 3 most important pages to improve.
- Pick one of the three pages.
- Improve it.
- Rinse and repeat.
Goals / Use Cases
tbd
Non Goals
tbd
Design
tbd
Bugs
Bug 479922 - Network error pages should give me tools instead of asking me questions
Reference
nsDocShell::DisplayLoadError -- dispatches various error pages
about:neterror
about:config -- urlclassifier.alternate_error_page default string = "blocked" -- for example -- tells nsDocShell::DisplayLoadError to use the "blocked" page instead of the default generic page.
https://johnath.com/ -- triggers a "Secure Connection Failed" error page.
http://example.example.com/ -- triggers an "Address Not Found" error page.
Error Types
Which ones do we want to improve first?
- neterror
- protocolNotFound
- fileNotFound
- dnsNotFound
- connectionFailure
- netInterrupt
- netTimeout
- nssBadCert
- nssFailure2
- phishingBlocked
- malwareBlocked
- malformedURI
- redirectLoop
- unknownSocketType
- netReset
- netOffline
- isprinting
- deniedPortAccess
- proxyResolveFailure
- proxyConnectFailure
- contentEncodingError
- unsafeContentType