With the HAProxy 2.6, the double header enconding configured at the application level is generating disruption on criticals customer services.
Cluster Admin is requesting if is possible to get a procedure to identify those application header from OCP in order to anticipate the potencial issue reported at solution https://access.redhat.com/solutions/7055002 before upgrading the cluster to OCP 4.14
This is a blocker for biggest account as Support Exception are being requested to deploy older version of HAProxy on  OCP 4.14 clusters

    4.14

    Reported at slack thread https://redhat-internal.slack.com/archives/CCH60A77E/p1724247463732519

    1. With an  OCP 4.14 route:
$ curl -kv --header 'Content-Type: application/json' --data '{"code": 0}' -H "transfer-encoding: chunked" -H "transfer-encoding: chunked" --resolve httpd-ex-sunbro.apps.sunbro3.la
b.psi.pnq2.redhat.com:80:10.74.208.127 http://httpd-ex-sunbro.apps.sunbro3.lab.psi.pnq2.redhat.com     
...
> Content-Type: application/json 
> transfer-encoding: chunked 
> transfer-encoding: chunked 
> 
< HTTP/1.1 400 Bad request 
< Content-length: 90 
< Cache-Control: no-cache 
< Connection: close 
< Content-Type: text/html     

    502/400 error results

200 OK