fix(security): allow disabling proxy signing with security: false#790
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis PR adds support for disabling proxy security in the Nuxt Scripts module. The Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
⚔️ Resolve merge conflicts
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 |
…urity # Conflicts: # docs/content/docs/1.guides/2.first-party.md
commit: |
🔗 Linked issue
Follow-up to #789 / #783
❓ Type of change
📚 Description
#789 added a
security.pageTokenflag, but disabling only the token still leaves signing enforcement on, so client-side reactive proxy calls 403. This replaces that with a single, complete opt-out.securitynow acceptsfalse. When set, the module resolves no secret, auto-generates nothing into.env, skips the page token plugin, andwithSigningpasses proxy requests through without verification. This gives a deterministic SSR payload (stableetag) with no partial-security footguns. Docs updated.