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
This is completely fine unless your external auth service returns cookies and other headers that exceed the default proxy buffer (4Kb). The configmap option proxy-buffer-size is completely missing its proxy_buffer_size equivalent in the block above.
What you expected to happen:
I expect that my settings are propagated to the config; at least the buffering options:
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
If the External Auth service returns for instance cookies that are bigger then 4Kb the request fails. See more details below.
NGINX Ingress controller version:
Kubernetes version (use
kubectl version
):Environment:
uname -a
): Linux ... 3.10.0-693.21.1.el7.x86_64 Basic structure #1 SMP Wed Mar 7 19:03:37 UTC 2018 x86_64 x86_64 x86_64 GNU/LinuxWhat happened:
When you create a Ingress resource like this one:
Controller generates a block like this one:
This is completely fine unless your external auth service returns cookies and other headers that exceed the default proxy buffer (4Kb). The configmap option
proxy-buffer-size
is completely missing itsproxy_buffer_size
equivalent in the block above.What you expected to happen:
I expect that my settings are propagated to the config; at least the buffering options:
How to reproduce it (as minimally and precisely as possible):
Any Ingress with external auth generates the block above.
Anything else we need to know:
no
The text was updated successfully, but these errors were encountered: