https://bz.apache.org/bugzilla/show_bug.cgi?id=65348
--- Comment #8 from nemo <[email protected]> --- 18:16 < SergioB> There are read/write timeouts in 0.4 that aren't present in 0.5. Disabling those prevented the issue. (read_timeout = 0 write_timeout = 0) The timeout values by default are 5 seconds. There was no point during trace6/trace8 where packets took longer than 5 seconds it seems to me... But perhaps there was some bug in the implementation. Still odd it only triggered with Apache's RATE_LIMIT and not wget/curl - I guess that might be the only thing the Apache people might be interested in, in case the module has some odd behaviour. I know httpd has a long history of working around issues in other clients/servers ☺ But under circumstances going to guess this is a low priority bug. ☺ -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
