fix(serve): reject opaque Origin null in CSRF guard#113
Conversation
Align the Origin fallback with the documented threat model: browsers that send Origin (including the literal "null" opaque value) are blocked on state-changing routes; curl-style clients without Origin still pass.
🦋 Changeset detectedLatest commit: 961e7ac The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Summary
Origin: nullexemption incsrfCheckso opaque browser contexts cannot POST to loopbackcodemap serve.Origin: nullagainstsave_baseline.Test plan
bun test src/application/http-server.test.ts