gateway-api
gateway-api copied to clipboard
Gateway API validations too strict for redirect status codes
What happened: Gateway API has validations that only account for 301 and 302 HTTP Redirects. https://github.com/kubernetes-sigs/gateway-api/blob/1edf7e93ae4bb8c5ea5cc2193586cfe1e5d15e2f/apis/v1/httproute_types.go#L1069
What you expected to happen: RFC 2616 defines several other redirects, including: 303, 304, 305, and 307.
Anything else we need to know?: Ask would be to align enum validations to RFC2616 section 10.3
Thank you!