On Thu, Nov 5, 2015 at 9:36 AM, Julien Vermillard <[email protected]> wrote: > 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
Hi Julien, You want to break compliency with HTTP RFC? https://tools.ietf.org/html/rfc7230#section-3.1.1 I'm against such change as a default behavior. Maybe you could simply upgrade the code of "option accept-invalid-http-request" to meet your requirement. http://cbonte.github.io/haproxy-dconv/snapshot/configuration-1.6.html#4.2-option%20accept-invalid-http-request Or create a new option "option accept-broken-http-version-from-client" :) Baptiste
