[openstreetmap/openstreetmap-website] Render errors rather than redirecting? (Issue #3876)

Andy Allan notifications at github.com
Fri Jan 6 13:39:08 UTC 2023


We currently have a few "error" pages, including from the errors_controller but also other pages like site_controller/offline. To show these pages, users typically go through this flow:

* Attempt to view page A
* Something in A triggers an error
* User receives a redirect to the error page B
* User views the error on page B

It's not clear to me what advantage, if any, there is being redirected. The alternative would be that when an error (or similar) is reached in the controller, it renders the error page from a shared template. That avoids having any redirects, and it avoids changing the URL. For example, if you find a page that triggers a 500 internal server error, your can copy the link into the bug report more easily :smile:

I haven't come across any other sites that follow this redirect-to-error-page approach. I'm curious as to whether this is deliberate or whether it's just happened this way over for historical reasons.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/3876
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/openstreetmap-website/issues/3876 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20230106/3978879e/attachment.htm>


More information about the rails-dev mailing list