I tries capture the close connection in the service associate with the ingress-nginx but I cant find a way. When this situation occur the log of nginx shows the correct status code on log:

172.21.0.224 - user [29/Apr/2024:13:21:41 +0000] "POST /execute HTTP/1.1" 499 0 "-" "Apache-HttpClient/4.5.12 (Java/1.8.0_382)" 409 2.702 [service-8080] [] 172.21.72.106:8080 0 2.702 - da6c85d6276498086c97ccb1380ed096

But in the service the process continue. I think the correct behavior is the nginx close the connection with the service to interrupt the process.

I'm following the instructions to install on [aws](https://kubernetes.github.io/ingress-nginx/deploy/#aws) changing only VPC CIDR and ACM. I installed the version 1.10.0 on k8s version 1.29.

In the documentation I only found the flag proxy_ignore_client_abort .

Have a way to change this behavior?
499 reflect on service
This is a GitHub Issue
repo:ingress-nginx
owner:kubernetes
Title : 499 reflect on service
Issue date:

--- start body ---
I tries capture the close connection in the service associate with the ingress-nginx but I cant find a way. When this situation occur the log of nginx shows the correct status code on log:

172.21.0.224 - user [29/Apr/2024:13:21:41 +0000] "POST /execute HTTP/1.1" 499 0 "-" "Apache-HttpClient/4.5.12 (Java/1.8.0_382)" 409 2.702 [service-8080] [] 172.21.72.106:8080 0 2.702 - da6c85d6276498086c97ccb1380ed096

But in the service the process continue. I think the correct behavior is the nginx close the connection with the service to interrupt the process.

I'm following the instructions to install on [aws](https://kubernetes.github.io/ingress-nginx/deploy/#aws) changing only VPC CIDR and ACM. I installed the version 1.10.0 on k8s version 1.29.

In the documentation I only found the flag proxy_ignore_client_abort .

Have a way to change this behavior?
--- end body ---
