-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make use of 404 template? #602
Comments
Hi @k0nsl , The 404 template was introduced by #430 / #444, it is rendered in the following situations:
A 404 should only be returned/displayed/rendered when the user/client attempts to access a resource that does not exist. The situation of a user running a search query that returns no result -either because there are no entries corresponding to the aforementioned query, or said user does not have access to some (private) results- is a nominal case, and will not lead to returning a 404 error page. Now regarding the addition of a 403 template:
|
404 is only rendered when a small hash isn't found, despite propositions in #430. Maybe, it can be re-discussed. About the login, displaying an error page is not ergonomic. When you mistype your password, you expect to be able to retype it again in the same page (using blank keycaps, you learn that the hard way). |
a 404 page on For the |
I'm wondering if anyone is working on actually making use of the
404.html
template in thetpl
directory. This could and probably should be used for when searches and tags return no results.The same principle could be used to generate 403s upon failed login attempts; just create a
403.html
template and modify the content accordingly.I tried searching the code and found no references that makes use of the
404.html
templateThe text was updated successfully, but these errors were encountered: