Hi,
When we migrated from Apache HTTPD to HA Proxy we found a strange problem.
We have some old HTTP client (embedded devices) which send a trailling
whitespace after the HTTP version.
The send: "GET HTTP/1.1 <CR>" in place of "GET HTTP/1.1<CR>"

HAProxy just drop the message sending a 400 error, HTTPD accept it.

It's not a big code change for making haproxy resilient to that, but I
wonder if you would accept a patch for that or you think you don't want
haproxy to be resilient to such behaviour?

Thanks,
Julien

Reply via email to