feat: bypass built-in CORS handling for shared ports #15684
Closed
Conversation
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
Signed-off-by: Danny Kopping <danny@coder.com>
Signed-off-by: Danny Kopping <danny@coder.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Don't review yet, incomplete
This PR is stacked upon
dk/cors! Merge this first!This PR builds upon the CORS bypass functionality introduced in #15669. It will enable template authors to disable our built-in CORS handling across all shared ports in all workspaces using the template.
Note: I copied the sharing level approach here and implemented this at the template level rather than the template version level, so operators won't be able to gradually phase this in. We have backwards-compatibility so this shouldn't be an issue.
Not loving that widowed word on the left, copy suggestions welcome