-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Opening an invalid direct link triggers a error exception page #952
Comments
Yes agreed. I'll take care of this. |
Do we want to show the actual 404 page or just redirect to files? |
rullzer
added a commit
that referenced
this issue
Aug 19, 2016
Fixes #952 * Use only the index route (since it went to showFile anyways) * Fix tests * Use getUserFolder to force init of users mounts
Fix is in #956 |
rullzer
added a commit
that referenced
this issue
Aug 23, 2016
Fixes #952 * Use only the index route (since it went to showFile anyways) * Fix tests * Use getUserFolder to force init of users mounts
rullzer
added a commit
that referenced
this issue
Aug 23, 2016
Fixes #952 * Use only the index route (since it went to showFile anyways) * Fix tests * Use getUserFolder to force init of users mounts
GitHubUser4234
pushed a commit
to GitHubUser4234/server
that referenced
this issue
Aug 30, 2016
Fixes nextcloud#952 * Use only the index route (since it went to showFile anyways) * Fix tests * Use getUserFolder to force init of users mounts
This was referenced Apr 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To reproduce access an not existing invalid direct link such as https://cloud.nextcloud.com/f/1357
This should be caught instead and a 404 be displayed instead of spamming the server log.
The text was updated successfully, but these errors were encountered: