You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a user comes across one of the error pages, it would be good if you could (optionally) display a “Go Back” button and take the user back to the start page.
Suggest a solution
Support option for a “Go Back” button with a defined URL.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Hello there! Since the same error pages can be used across multiple domains, websites, or paths, I believe using a static URL for user redirection might not be very effective. What are your thoughts on this?
For example, if a user mistypes something, encounters an error, ... he first receives the error message page, but then can simply return to a defined start page (e.g. a dashboard, intranet, website, ...) via a “Go Back” button if he wants.
Let me elaborate on the potential issue I foresee: imagine using the error pages with Traefik, which serves websites on two domains, such as app1.com and app2.com. If a user encounters a 404 error on app1.com, how should the error pages determine that the "Go Back" link should redirect to app1.com instead of app2.com? Where would the necessary URL come from?
Is there an existing issue for this?
Describe the problem to be solved
If a user comes across one of the error pages, it would be good if you could (optionally) display a “Go Back” button and take the user back to the start page.
Suggest a solution
Support option for a “Go Back” button with a defined URL.
Additional context
No response
The text was updated successfully, but these errors were encountered: