New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cors: add unmatched_preflights #3171
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
networking/v1/virtual_service.proto
Outdated
enum UnmatchedPreflights { | ||
// Preflight requests not matching the configured allowed origin | ||
// will be forwarded to the upstream. | ||
FORWARD = 0; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would set 0 to UNSPECIFIED. If we do forward = 0
, we can never change our mind in the future and make 'ignore' the default. Even if we don't plan to now, its best to be precise
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated
xref: envoyproxy/envoy#33051
Introduce
forward_not_matching_preflights
allow to return local reply when preflight origin does not match allowed origins.API: #3171