-
Notifications
You must be signed in to change notification settings - Fork 94
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
Core API: Exact PathMatch #476
Labels
area/httproute/core
Relates to all Core features of HTTPRoute
enhancement
New feature or request
refined
Requirements are refined and the issue is ready to be implemented.
Milestone
Comments
kate-osborn
added
enhancement
New feature or request
area/httproute/core
Relates to all Core features of HTTPRoute
and removed
proposal
labels
Mar 21, 2023
kate-osborn
added
the
refined
Requirements are refined and the issue is ready to be implemented.
label
Mar 24, 2023
When we say "if two rules have the same path", does this consist of two separate rules, or two separate matches within a rule, or both? |
two separate rules however, |
6 tasks
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/httproute/core
Relates to all Core features of HTTPRoute
enhancement
New feature or request
refined
Requirements are refined and the issue is ready to be implemented.
Support
Exact
PathMatchType
in HTTPRoute resource. See https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.PathMatchTypeAcceptance criteria:
Appendix:
Two locations with the same path but different matching (exact and prefix)
Aha! Link: https://nginx.aha.io/features/NKG-60
The text was updated successfully, but these errors were encountered: