Hi Andy, On Sat, Feb 22, 2014 at 09:50:50AM -0600, Andy Walker wrote: > I also thought I'd include this for posterity -- it was some out-of-band > communication with Willy, which I hope he doesn't mind me including.
no problem. > On Sat, Feb 22, 2014 at 1:40 AM, Willy Tarreau wrote: > > > OK thanks. So what it looks like is that MSIE is using the awful > > preconnect mechanism that its competitors chrome and firefox use > > as well, but the difference is that it doesn't know how to do it > > correctly! Because as you can see, there's no request sent over > > the connection in 10 seconds. And it starts using it after receiving > > the close... > > > I suppose it's wrong for me to be responding to that in a different thread, > but I'll give it a shot anyway. I wholeheartedly agree that IE is doing > multiple things wrong, here... making a request after the FIN, as well as > reading a response that was made before the request was even made. However, > I'm a bit confused as to why HAProxy was sending a 408 at all in this > instance. There wasn't a request made prior to it sending that 408, so > something seems a bit fishy there, too. I could be completely missing > something, though. It's *exactly* the purpose of 408 : indicate to the client that we're fed up with waiting for it to send a request (hence the "request timeout" message). https://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-26#section-6.5.7 > > You should try to clear the 408 message to see if MSIE handles the > > situation any better. But that would be a shame, because this message > > exists exactly for this purpose and all web servers emit it, so all > > MSIE users are bothered by this stupid bug. > > In order to do this, just add the following in your frontend : > > > > errorfile 408 /dev/null > > > Good call! It sounds to me like that would be a reasonable workaround for > these folks using IE. A bummer for everyone else, but hopefully they won't > be adversely affected. I'll change my timeouts back to the more-sane 10 or > 15 seconds, and start using a null 408 error file to see what the reports > from our users sound like. It shouldn't be too long before we have an idea > if that helped or not. Great, keep us informed about the result! Cheers, Willy
