-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
fix: Skip CSRF check if there's JSON content type #39658
Conversation
WalkthroughThe changes add a new check in the Changes
Sequence Diagram(s)sequenceDiagram
participant Req as Request
participant Cfg as CsrfConfigCE
Req->>Cfg: Call matches(request)
alt Content-Type is APPLICATION_JSON
Cfg-->>Req: Return notMatch()
else Other Content-Types
Cfg->>Cfg: Evaluate existing header and GET checks
Cfg-->>Req: Return appropriate match result
end
Suggested labels
Suggested reviewers
Poem
📜 Recent review detailsConfiguration used: .coderabbit.yaml 📒 Files selected for processing (1)
⏰ Context from checks skipped due to timeout of 90000ms (2)
🔇 Additional comments (2)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
Description
Automation
/test sanity
🔍 Cypress test results
Caution
If you modify the content in this section, you are likely to disrupt the CI result for your PR.
Communication
Should the DevRel and Marketing teams inform users about this change?
Summary by CodeRabbit
This update enhances the handling of API interactions involving JSON data, resulting in a more seamless integration experience. The system now applies streamlined processing for JSON requests, reducing unnecessary verifications and improving overall performance and responsiveness for API-based communications.