🛡️ Sentinel: [HIGH] Fix missing Vary header for dynamic CORS reflection

[EffortlessSteven]

🚨 Severity: HIGH
💡 Vulnerability: The dynamic Origin header reflection in CORS middlewares was missing the accompanying Vary: Origin header.
🎯 Impact: Intermediate caches (like CDNs or proxies) might cache the response for one origin and serve it to subsequent requests from different origins, leading to cache poisoning and unauthorized cross-origin access.
🔧 Fix: Appended Vary: Origin when dynamically reflecting the Origin header in Access-Control-Allow-Origin responses.
✅ Verification: Ran cargo test for http-middleware and app-http to ensure CORS logic tests continue to pass with the new headers.

---

PR created automatically by Jules for task 10382960127897132322 started by @EffortlessSteven

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[coderabbitai]

Warning

Rate limit exceeded

@EffortlessSteven has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 19 minutes and 13 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: be8b2e72-944a-4695-b353-10eceeef17af

📥 Commits

Reviewing files that changed from the base of the PR and between 90fd4d1 and c0e5c39.

📒 Files selected for processing (3)

• .jules/sentinel.md
• crates/app-http/src/middleware/cors.rs
• crates/http-middleware/src/cors.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch sentinel/fix-cors-vary-origin-10382960127897132322

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 0/1 reviews remaining, refill in 19 minutes and 13 seconds.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Test Results

283 tests   245 ✅  11m 2s ⏱️
 25 suites   38 💤
  1 files      0 ❌

Results for commit c0e5c39.