https://bz.apache.org/bugzilla/show_bug.cgi?id=69355
Chen Jp changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=69355
--- Comment #5 from Remy Maucherat ---
(In reply to Chen Jp from comment #4)
> (In reply to Remy Maucherat from comment #3)
> > I see a trend in the PRs that you are submitting. Trying to be as precise as
> > possible is a commendable goal, but
https://bz.apache.org/bugzilla/show_bug.cgi?id=69355
--- Comment #4 from Chen Jp ---
(In reply to Remy Maucherat from comment #3)
> I see a trend in the PRs that you are submitting. Trying to be as precise as
> possible is a commendable goal, but the problem is that this exactitude does
> not mak
https://bz.apache.org/bugzilla/show_bug.cgi?id=69355
Mark Thomas changed:
What|Removed |Added
Severity|normal |enhancement
--
You are receiving this m
https://bz.apache.org/bugzilla/show_bug.cgi?id=69355
--- Comment #3 from Remy Maucherat ---
I see a trend in the PRs that you are submitting. Trying to be as precise as
possible is a commendable goal, but the problem is that this exactitude does
not make much sense in the context of Tomcat since
https://bz.apache.org/bugzilla/show_bug.cgi?id=69355
--- Comment #2 from Igal Sapir ---
(In reply to Chen Jp from comment #0)
> Currently, RateLimitFitler implements a roughly rate limit algorithm,
> provides closely but not exactly equality with user's configuration. For
> example, configuration
https://bz.apache.org/bugzilla/show_bug.cgi?id=69355
Chen Jp changed:
What|Removed |Added
OS||All
--- Comment #1 from Chen Jp ---
add PR
