Not logged in access attempts show 500er instead of 404

[seb-kw]

Currently, the web always displays 500er error pages when trying to access a project without access rights or when not logged in. In these cases, a 404 page should be shown. In case a user is not logged in, a notice should be shown on that page.

[gauravshinde1729]

Hey @seb-kw

• Should 401 (unauthenticated) and 404/403 (authenticated but unauthorized) be treated identically on the frontend (both show 404 page), or should they route differently (e.g., 401 redirects to login page)?

• Should the "not logged in" notice on the 404 page include a direct link to the login page or just a text message?

[timbastin]

Hey @seb-kw

• Should 401 (unauthenticated) and 404/403 (authenticated but unauthorized) be treated identically on the frontend (both show 404 page), or should they route differently (e.g., 401 redirects to login page)?

• Should the "not logged in" notice on the 404 page include a direct link to the login page or just a text message?

What do you think about having dedicated pages for each of that status codes. So one for a real 500, one for 401, 403, 404. I think we should be able to get the logged in state for the user on those pages as well. It would be helpful to have a good error message and show the user the current logged in user information or a button to login (routing to /login). What do you think @seb-kw @gauravshinde1729

[seb-kw]

having dedicated pages for each of that status codes

That would be the nicest solution. The button pointing to /login should then always be visible.

Nice would also be a button to create a GitHub Issue. Especially on the 500er error page.