kubernetes-sigs / kubernetes-sigs/gateway-api
CORS - Followup on suggested improvements
- Dominant language
- Go
- Stars
- 3k
- Forks
- 789
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 45
Description
**What would you like to be added**:
Followup on suggested improvements for CORS:
- https://github.com/kubernetes-sigs/gateway-api/pull/3739/files#r2667680110 - Fix header ordering, do not introduce the IgnoreWhiteSpace
- https://github.com/kubernetes-sigs/gateway-api/pull/3739/files#r2731132648 - Introduce HeaderAsList for the ordering validation
- https://github.com/kubernetes-sigs/gateway-api/pull/3739/files#r2690157156 - Followup on allowCredentials and wildcard usage for methods (this is a proxy behavior)
**Why this is needed**:
Move with CORS promotion during RC cut, and followup with implementations on conformance improvements
/cc @snorwin @DamianSawicki @zhaohuabing
Contributor guide
Research direction
Start with the referenced PR #3739 review discussions and the repository's current CORS conformance implementation. Trace the tests and code covering header ordering, HeaderAsList, and allowCredentials with wildcard methods; done means the follow-up behavior is implemented and the relevant conformance checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100