Nginx default error page 400 has shown also when custom error pages is active

[StenoSanna]

We are using ingress-nginx (version 4.11.3 and controller image 1.11.3) as reverse-proxy frontend of our web application. With the custom-error-pages configuration we manage the error pages but we have an issue when the ingress tries to redirect errors to a named location during the early request processing phase when the request URI is not yet parsed. In this case the 400 default page has shown. Has someone met the same issue? How has it been resolved?? We have also tried to remove the "nginx" from the 400 standard page but there seems no way to do that.
R
Stefano

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[github-actions]

This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #ingress-nginx-dev on Kubernetes Slack.