Allow to customize HTTP errors
Submitted by Javier Muñoz
In some use cases where the user operates under a limited user experience (e.g. kiosk mode configurations and so on), http error pages require customization to avoid surfing blocking.
In this context, when a server returns http errors (e.g 404) the user could get stuck in the error page (as he has no menus to come back to the previous one). This kind of situation would require a customizable management of HTTP client (4xx) and server (5xx) errors.
The initial behavior would be to redirect the user to the homepage, or load an alternate HTML (that could be local HTML file showing links to go to the homepage or come back).
Version: git master