[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug 62362] Proxied content not properly rate-limited


--- Comment #2 from Luca Toscano <toscano.luca@xxxxxxxxx> ---
The attached patch seems to work on my test case scenarios. What I did was:

* created a ~4M text file containing lines like TEST 0, TEST 1, TEST 2, etc..
* served the file directly from httpd (via Directory config) and also via
Python 3's http server and proxied via mod_proxy_http.
* calculated the sha1sum of the files generated redirecting curl's output to a
* noted time spent in both cases to rate limit the content with various rate
limit speeds (via curl's average dload speed).

Everything seems consistent and fine as far as I can see, the patch seems to
work as expected. This is a rather invasive refactoring of the rate-limit
filter so I might have missed something, testing/feedback/suggestions/reviews
are really welcome :)

You are receiving this mail because:
You are the assignee for the bug.
To unsubscribe, e-mail: bugs-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: bugs-help@xxxxxxxxxxxxxxxx