Cyril Bonté said the following on 02/19/2014 10:44 PM: [CUT] > I really think there isn't any issue. > > Remember that some browsers (such as chrome/chromium) preopen connection > in case there is a need to ask for more requests in parallel. > > While hitting F5, the browser will ask to close those connections. As > there was no data, no valid request was received on the haproxy side and > haproxy logs a 408. > Using f5 to reproduce is just my way of reproducing.. it happens randomly while people work on the site (not pressing f5).
> I'm pretty sure that adding "option dontlognull" [1] will solve the > "issue". > I added this in defaults section - it didn't change anything. I set option http-keep-alive (and removed http-server-close) as well. I'm running dev22. > Also, as a side note, your configuration is not optimal : > - you are using both "option httpclose" and "option http-server-close", > you should make a choice (or use "option http-keep-alive" in recent > haproxy 1.5 dev versions). > - the "balance" keyword is not valid in a frontend section. > - you should avoid the use of "stats enable" in the defaults section. > my bad - I've removed that. -- Regards, Klavs Klavsen, GSEC - [email protected] - http://www.vsen.dk - Tlf. 61281200 "Those who do not understand Unix are condemned to reinvent it, poorly." --Henry Spencer
