You can't split a webapp into protected and not protected with the
valve. It's all or nothing. You'd be better off implementing a filter
in your webapp that pay's attention to request.getRemoteAddr() and
either chains the request or redirects to an error page.
--David
Peter Neu wrote:
I ju
> From: David Smith [mailto:[EMAIL PROTECTED]
> Subject: Re: AW: Problem with RemoteAddrValve in Context.xml
>
> I suspect the context.xml file in META-INF isn't honored unless you
> deploy your webapp as a web archive file (.war).
Not true - META-INF/context.xml is used r
I suspect the context.xml file in META-INF isn't honored unless you
deploy your webapp as a web archive file (.war). Sounds to me like this
webapp is an exploded folder under webapps directory. In that case,
copy the context.xml file to Catalina/localhost, rename to match your
web application's c
Should work as is with the allow expression typed either way. Do you
have Apache httpd or something similar acting as a proxy server at
192.168.200.188? A quick diagnostic might show if this is the case:
http://java.sun.com/JSP/Page";>
http://www.w3.org/1999/xhtml"; l
