You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In virtual server validation, if a virtual server route does not have the virtual server path as prefix, it will be rejected. In the specific where the subroute is a regex path, however, the validation fails to reject an invalid virtual server route definition, where a subroute path does not have the virtual server path as prefix.
To Reproduce
Steps to reproduce the behavior:
deploy the following virtual server and virtual server route:
Virtual server path:
Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂
Cheers!
haywoodsh
changed the title
Virtual Server routes
Virtual Server validation does not reject subroute path with regex that do not match virtual server path
Nov 30, 2023
haywoodsh
changed the title
Virtual Server validation does not reject subroute path with regex that do not match virtual server path
Virtual Server validation does not reject regex subroute paths that do not match virtual server path
Nov 30, 2023
Describe the bug
In virtual server validation, if a virtual server route does not have the virtual server path as prefix, it will be rejected. In the specific where the subroute is a regex path, however, the validation fails to reject an invalid virtual server route definition, where a subroute path does not have the virtual server path as prefix.
To Reproduce
Steps to reproduce the behavior:
deploy the following virtual server and virtual server route:
Virtual server path:
virtual server route:
Expected behavior
The virtual server route with incorrect subroute path should be rejected during validation
Additional context
This could be the possible code snippet that should return an error message but does not.
https://github.com/nginxinc/kubernetes-ingress/blob/main/pkg/apis/configuration/validation/virtualserver.go#L1482-L1485
The text was updated successfully, but these errors were encountered: