Hi Willy, On 07:57 Sun 06 Apr , Willy Tarreau wrote: > > In fact I intentionally made this choice because Apache does the same and > wanted to ensure the least possible breakage by inserting haproxy in front > of it (you can't imagine how users are picky when something does not work > anymore after they install your product). But I agree that the URI is > mandatory according to the RFC, and even according to Tim BL's original > WWWDaemon (which used to only process GET requests containing a URI). > > These days we don't need to prove that we don't break anything, so I think > it's fine to change this behaviour. So I have merged your patch into 1.5. > I don't intend to backport it into 1.4-stable however.
Thanks! I already suspected that you had your reasons for this, but having the req_proto_http ACL match requests like "HEAD HTTP/1.0" as valid seemed a bit strange! Just for the record, Apache 2.2 still accepts URI-less requests, nginx exhibits our "new" behavior and varnish requires a request URI but does not mandate GET for HTTP/0.9 requests. Regards, Apollon
