> Using RemoteAddrValve as <Host/> subelement won't work, as will
>apply to both, any suggestions?
Why not just do:
<Host name="www.mydomain.com" ...... >
<Context path="" docBase="" debug="0" ..... />
</Host>
<Host name="www-i.mydomain.com <http://www.mydomain.com/>" ...... >
<Context path="" docBase="" debug="0" ..... />
</Host>
Ofcourse I'm pretty new to this so you might see some cons to this :)
Cheers,
- Pulkit
On 1/20/06, Patricio Keilty <[EMAIL PROTECTED]> wrote:
>
> Hi,
> I need to restrict access to my webapp to some IP adresses on a per-domain
> name
> basis. In our tomcat server we are using an <Alias/> element to serve both
> domains from same host as the following config shows:
>
> <Host name="www.mydomain.com" ...... >
> <Alias>www-i.mydomain.com</Alias>
> <Context path="" docBase="" debug="0" ..... />
> </Host>
>
> Is it possible to use a RemoteAddrValve for each domain, each which
> different IP
> address sets? Using RemoteAddrValve as <Host/> subelement won't work, as
> will
> apply to both, any suggestions?
>
> Thanks,
> --p
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
