We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
apilogs
It seems at the moment that any user can see the logs (in /apilogs); obviously this could be a security issue.
It could be optional to protect that route(s) with a guard (which could be configurable).
The text was updated successfully, but these errors were encountered:
I am thinking about it too. I'll handle this one.
Sorry, something went wrong.
This is a must. Else detailed info, and info valuable with regards to marketing (e.g number of requests or day) is visible to public.
I was thinking the requesting user id should also be logged, in which case the apilogger view definitely needs to be guarded.
(Look at how larecipe guards and defined it's routes. Not that hard)
Thanks I will definitely look into it.
Added in #42
No branches or pull requests
It seems at the moment that any user can see the logs (in /apilogs); obviously this could be a security issue.
It could be optional to protect that route(s) with a guard (which could be configurable).
The text was updated successfully, but these errors were encountered: