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
Various users are reporting 431 Request header fields too large errors when issuing requests to meshed targets.
How should the problem be solved?
We need to determine first the circumstances under which this happens. Once that's clearer we can either increase the default for max_header_list_size, or expose a config for it.
Any alternatives you've considered?
Currently the workaround is to use additionalEnv, which is just an escape hatch: