Skip to content
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.

Sign up for GitHub

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

Jump to bottom

The caseSensitiveHttpHeaders property is not available in APPolicy CRD #3111

Closed
aknot242 opened this issue Sep 29, 2022 · 1 comment · Fixed by #3133
Closed

The caseSensitiveHttpHeaders property is not available in APPolicy CRD #3111

aknot242 opened this issue Sep 29, 2022 · 1 comment · Fixed by #3133

Comments

@aknot242
Copy link
Contributor

aknot242 commented Sep 29, 2022 •
edited
Loading

The caseSensitiveHttpHeaders property is not present in the APPolicy CRD. There are customers that require this in order to quickly mitigate the effects of using downstream proxies that mutate header casing, such as Envoy does

The setting is documented here, but is missing in the CRD here:
https://github.com/nginxinc/kubernetes-ingress/blob/2bd2646b6555b09334227ca09971609389968944/deployments/common/crds/appprotect.f5.com_appolicies.yaml#L335
@github-actions
Copy link

Hi @aknot242 thanks for reporting!

Be sure to check out the docs while you wait for a human to take a look at this 🙂

Cheers!

@aknot242 aknot242 changed the title The caseSensitiveHttpHeader property is not available in APPolicy CRD The caseSensitiveHttpHeaders property is not available in APPolicy CRD Oct 2, 2022
@aknot242 aknot242 mentioned this issue Oct 2, 2022
Closed
6 tasks
@galitskiy galitskiy mentioned this issue Oct 7, 2022
Merged
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@aknot242