-
Notifications
You must be signed in to change notification settings - Fork 342
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
[docs] Make clear that sesskey is CSRF token. #1083
Conversation
✅ Deploy Preview for moodledevdocs ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
⚡️ Lighthouse report for the deploy preview of this PR
|
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.
Thanks for adding the clarification. Just a few tidyups.
general/development/policies/security/crosssite-request-forgery.md
Outdated
Show resolved
Hide resolved
general/development/policies/security/crosssite-request-forgery.md
Outdated
Show resolved
Hide resolved
general/development/policies/security/crosssite-request-forgery.md
Outdated
Show resolved
Hide resolved
Thanks Andrew! |
Co-authored-by: Andrew Lyons <[email protected]>
Squashed Andrews's improvements and rebased. Kindly asking @mickhawkins to review it and merge. Thanks! :) |
sesskey
is often confused with Moodle Session ID cookie. This change updates Session Key section at Cross-site request forgery page, clarifying its purpose as CSRF token.Rendered page: https://deploy-preview-1083--moodledevdocs.netlify.app/general/development/policies/security/crosssite-request-forgery#session-key