On Sun, Sep 23, 2012 at 02:16:49PM +0200, Cyril Bonté wrote:
> And Willy added some documentation about that (with a note about Apache 
> allowing non-ascii characters) :
> http://haproxy.1wt.eu/git?p=haproxy.git;a=commit;h=2f1feb99a5499510183f398730cddc2a7e7df863
> 
> So, it looks like the only alternative is to add "option 
> accept-invalid-http-request" in your frontend configuration.

I tried to add "option accept-invalid-htttp-request" to the section
default, but haproxy still gives badrequest.

-- 
BRGDS. Alexey Vlasov.

Reply via email to