Hi, On Tue, Oct 21, 2014 at 02:50:58PM +0200, Robert Bartl wrote: > yep. that worked around the broken URL. > > BTW. this behaviour started with Copy & Pasting a URL with an umlaut > into Internet explorer.
We've already had some cases where users had to use the option to accept invalid requests for MSIE which *sometimes* does not properly encode forbidden characters in the URI. Note that non-ascii characters are explicitly forbidden in the URI and the only reason some clients continue to send them is because they don't know they send them since many servers transparently accept them. And haproxy used to be one of them in the past. If you managed to reproduce it with Curl, you should probably contact Daniel Steinberg and give him your test case with the exact version. That will not fix MSIE but that will at least fix one client :-) Regards, Willy
