Browsing to a non-existing webpage should display a 5xx error page
See original GitHub issueExpected Behavior
Browsing to a non-existing address should display a 5xx error page.
Current Behavior
It shows a blank page (loads nothing)
Possible Solution
Update the DAppContainer component to listen for webview did-fail-load events. In such a case, render a custom component that gives details about the errorCode
and errorDescription
.
reference: https://github.com/nos/client/issues/188#issuecomment-395820523
Screenshot
Steps to Reproduce (for bugs)
- Surf to any website/dapp (either on the nOS OR http(s) protocol) that does not exist
- Look
Context
It’s not clear that it doesn’t exist
Your Environment
any
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (12 by maintainers)
Top Results From Across the Web
Displaying a Custom Error Page (C#) - Microsoft Learn
What this means for the web application in production is that if a user requests a page that is not found then they...
Read more >Web.config - Custom error pages not working - Stack Overflow
This seems to be most of the answer, but I've updated the question - There's still a problem when navigating to a nonexistent...
Read more >Creating an HTML 404! Error Web Page - Udacity
Learn how to create a Friendly and informative HTML 404! Error Web Page to help assist visitors that land on an old web...
Read more >How to Create Custom Error Pages in cPanel - InMotion Hosting
Lists the visitor's browser type. Redirect Status Code, This will display the error message code, such as 500, or 404, etc. Click the...
Read more >Custom error pages - Sitefinity CMS Setup and maintenance
Configure custom error pages to provide information to users about the problem with the resource they are trying to access.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry. To clarify, I meant the game in the 404 page. I don’t think a 404 page should be “future”.
Aren’t there two different cases, requestion unexisting host (cannot be resolved) and requesting a non-existent resource from a host. I believe in the first case nos client should show placeholder (nos domain cannot be resolved) but in the second case, it is the responsibility of a dApp to handle requests to non-existent pages (error 404) and errors (5xx).