Repository navigation
feat(http): expose optional tunnel CORS policies - #21
Merged
Merged
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
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.
Add immutable
HttpCors, expose it through tunnel options/builders, and preserve it in protocol request/response conversion. Existing constructors remain available. Reject private/non-HTTP use and align the additive wire schema with 1.4.6.Validation:
mvn -q spotless:apply verifyand finalmvn -q verify, including policy round-trip, absence and immutable-list tests. No release version change.Related: Engine #192 and Go #155. Engine must be deployed before clients using protocol 1.4.6. This is a source update for the next normal release; no dedicated SDK release or public changelog update is requested.