Add support for suffix domains in allowed origins in http input plugin #676
Conversation
This file contains 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
HeadHunter483
force-pushed
the
675-allowed-origin-suffix
branch
2 times, most recently
from
d9d7af6
to
2f6b6d9
Compare
DmitryRomanov
approved these changes
Sep 13, 2024
kirillov6
approved these changes
Sep 13, 2024
HeadHunter483
force-pushed
the
675-allowed-origin-suffix
branch
from
2f6b6d9
to
cd196d6
Compare
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.
Description
This pr adds wildcard support in CORS allowed origins in HTTP input plugin.
Only one wildcard per origin is allowed. E.g.
http://*.example.com- valid,http://*.example.*.com- invalid.Fixes #675