* Make configuration issue for RemoteAddrValve, RemoteHostValve result
in the failure of the valve rather than just a warning message.
Ensure changes to the configuration of these valves via JMX are thread-safe.
Refactor value matching logic into separate method.
Expose the new method isAllowed and isAllowValid, isDenyValid properties through JMX.
It is based on r1189256 and r1187027, r1198622
(r1189258, r1187029, r1198623 in TC7)
http://people.apache.org/~kkolinko/patches/2011-11-08_tc55_RequestFilterValve_v4.patch
+1: kkolinko,funkman,jim
-1:
kkolinko: It does its work and prevents app from starting and working. Though
1. Autodeployment prints the same error every 10s. It is OK, though a
bit annoying.
2. Application that failed to start responds with 403. I do not
understand why. I would expect 404 or 503.
3. Application that failed to start is not listed by the manager app.
It is expected, but does not explain why error 403 and not 404 is observed.
git-svn-id: https://svn.apache.org/repos/asf/tomcat/tc5.5.x/trunk@1221276 13f79535-47bb-0310-9956-ffa450edef68
4 files changed
