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
What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.): duplicate header, more_set_headers, proxy_hide_header, mismatching security header values
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.): This is a bug report
What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.): duplicate header, more_set_headers, proxy_hide_header, mismatching security header values
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
NGINX Ingress controller version: 0.26.1
Kubernetes version (use
kubectl version
):Same thing after updating to 1.14:
Environment:
uname -a
): 4.15.0-1034-gkeWhat happened:
Upstream sets Strict-Transport-Security like this:
When I examine the response headers of nginx-ingress using
curl -I
, I get:What you expected to happen:
The upstream header should have been replaced at nginx-ingress.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
The text was updated successfully, but these errors were encountered: