https://bz.apache.org/bugzilla/show_bug.cgi?id=65348
--- Comment #10 from nemo <[email protected]> --- Final update. I've been moved off onto other emergencies so won't be able to test my "Apache RATE_LIMIT is suddenly halting all traffic towards the end of a large transfer" theory. I also noticed one additional bug with Apache RATE_LIMIT that I may have time to write up properly someday. If the proxied server responds with 304 plus an empty body (as it does with If-None-Match of an existing ETag, I get an invalid request response with RATE_LIMIT enabled). ======== Read error (The request is invalid.) in headers. Retrying. ======== This happens in all browsers/clients - above is wget. No errors with rate_limit disabled. -- 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]
