Tengine 3.1.0: HTTP route and TLS enhancements without tengine reload based on tengine-ingress#1877
Merged
Conversation
…achine) based on ingress
…mod of header, cookie, query parameter while also being able to add HTTP headers and query parameter
add feature https_allow_http
TLS: allow support for different protocols on different hosts (same m…
…cement HTTP Route: supports routing based on multiple values, nginx var, or …
Collaborator
|
3.1.0 prerelease version |
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
2 participants
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.
No description provided.