As HAproxy2.6 is introduced in 4.14, and more and more of the customers are upgrading to 4.14 because of OCP4.12 is running out of support, the behavior that default block duplicate TE header cause a huge impact to customers, as they do not have enough time for their application team to update their code to fix the duplicate TE issue, on the other hand, HAproxy2.6.20 support the option `accept-invalid-http-response` which helps in mitigate the impact to customer, hence we would like to request to support this option in OCP4.14 future release

https://access.redhat.com/solutions/7055002