feat: add per-endpoint CORS override configuration#168
Closed
Uchechukwu-Ekezie wants to merge 1 commit into
Closed
feat: add per-endpoint CORS override configuration#168Uchechukwu-Ekezie wants to merge 1 commit into
Uchechukwu-Ekezie wants to merge 1 commit into
Conversation
- Export corsOverride() factory that merges per-route CorsOptions on top of the global defaults (allowedOrigins + credentials: true) - Global corsMiddleware() is unchanged — only routes that opt in are affected - JSDoc examples show webhook and export use-cases Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
@Uchechukwu-Ekezie Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #159
What changed
corsOverride(options)factory fromcors.middleware.tsCorsOptionson top of global defaults (allowedOrigins + credentials: true)corsMiddleware()and all existing routes are unchangedWhy
Some routes (public webhooks, file exports, partner integrations) need a different CORS policy than the app default. The override merges only what you specify so secure defaults are never accidentally dropped.
How to test
corsOverrideon any route and pass custom options (e.g.{ origin: '*', credentials: false })OPTIONSpreflight on that route should reflect the override