-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
fix(status): Avoid session creation for status requests #49406
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
Conversation
59d4d1d to
6140788
Compare
6140788 to
7395bfd
Compare
szaimen
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but didnt test
Signed-off-by: Git'Fellow <[email protected]>
85ccc8e to
33d7019
Compare
nickvergessen
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But since we have a valid request class in the place already, it should be fine
|
Hey, it looks like this broke the security scanner. See https://help.nextcloud.com/t/update-nextcloud-to-31-0-0-now-scaner-showing-rating-a/218485/13. So revert? |
|
Requests from scanner 1/month or 1/year We can add a force header to do the session or we scan a second endpoint. |
|
Resolved by #51184 |
Checklist