You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by dsc <ds...@yahoo.com> on 2008/05/27 16:52:43 UTC
Denying access to a webapp when accessing it through a specific DNS
name or IP Address
Hello,
Let's say I have a webapp, named test, which is deployed on server A.
Server A hast 2 DNS names, one for the Intranet: www.intranet.com
and one for the Internet www.internet.com
If a user accesses www.intranet.com/test, the webapp should be allowed to
run, but if the user accesses www.internet.com/test, the access should be
blocked.
I have found that through
<Valve className="org.apache.catalina.valves.RemoteAddrValve" ...
I can define for which client IP Addresses the access should be allowed, but
it would be much better for my purposes to make the decision to grant access
or not based on the URL used.
Thank you,
dsc
--
View this message in context: http://www.nabble.com/Denying-access-to-a-webapp-when-accessing-it-through-a-specific-DNS-name-or-IP-Address-tp17492267p17492267.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Denying access to a webapp when accessing it through a specific
DNSname or IP Address
Posted by dsc <ds...@yahoo.com>.
In this case it's actually ok not to allow access if an IP Address is used
or it could also be entered in the configuration.
The case here is the following. There's an eshop that is accessible through
/Eshop and its administration is accessible through /admin. /admin should be
allowed only when accessed through www.intranet.com/admin (intranet.com is
only visible in the Intranet) and should be blocked when accessed through
www.internet.com/admin.
Thanks
Caldarale, Charles R wrote:
>
>> From: dsc [mailto:dscouto@yahoo.com]
>> Subject: Denying access to a webapp when accessing it through
>> a specific DNSname or IP Address
>>
>> it would be much better for my purposes to make the decision
>> to grant access or not based on the URL used.
>
> And what would you like to happen when an IP address is used? It's safer
> to filter on the client rather than on how the client chooses to access
> the server (DNS names are not hard to fake).
>
> - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If you
> received this in error, please contact the sender and delete the e-mail
> and its attachments from all computers.
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Denying-access-to-a-webapp-when-accessing-it-through-a-specific-DNS-name-or-IP-Address-tp17492267p17493626.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Denying access to a webapp when accessing it through a specific
DNSname or IP Address
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: dsc [mailto:dscouto@yahoo.com]
> Subject: Denying access to a webapp when accessing it through
> a specific DNSname or IP Address
>
> it would be much better for my purposes to make the decision
> to grant access or not based on the URL used.
And what would you like to happen when an IP address is used? It's safer to filter on the client rather than on how the client chooses to access the server (DNS names are not hard to fake).
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Denying access to a webapp when accessing it through a specific
DNS name or IP Address
Posted by dsc <ds...@yahoo.com>.
Thanks, but I believe it also checks the Client DNS Name and not the URL
that is provided.
Len Popp wrote:
>
> Have you tried RemoteHostValve? (It's documented in the same place as
> RemoteAddrValve.)
> --
> Len
>
> On Tue, May 27, 2008 at 10:52 AM, dsc <ds...@yahoo.com> wrote:
>>
>> Hello,
>>
>> Let's say I have a webapp, named test, which is deployed on server A.
>>
>> Server A hast 2 DNS names, one for the Intranet: www.intranet.com
>>
>> and one for the Internet www.internet.com
>>
>> If a user accesses www.intranet.com/test, the webapp should be allowed to
>> run, but if the user accesses www.internet.com/test, the access should be
>> blocked.
>>
>> I have found that through
>>
>> <Valve className="org.apache.catalina.valves.RemoteAddrValve" ...
>>
>> I can define for which client IP Addresses the access should be allowed,
>> but
>> it would be much better for my purposes to make the decision to grant
>> access
>> or not based on the URL used.
>>
>> Thank you,
>> dsc
>> --
>> View this message in context:
>> http://www.nabble.com/Denying-access-to-a-webapp-when-accessing-it-through-a-specific-DNS-name-or-IP-Address-tp17492267p17492267.html
>> Sent from the Tomcat - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Denying-access-to-a-webapp-when-accessing-it-through-a-specific-DNS-name-or-IP-Address-tp17492267p17493568.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Denying access to a webapp when accessing it through a specific DNS name or IP Address
Posted by Len Popp <le...@gmail.com>.
Have you tried RemoteHostValve? (It's documented in the same place as
RemoteAddrValve.)
--
Len
On Tue, May 27, 2008 at 10:52 AM, dsc <ds...@yahoo.com> wrote:
>
> Hello,
>
> Let's say I have a webapp, named test, which is deployed on server A.
>
> Server A hast 2 DNS names, one for the Intranet: www.intranet.com
>
> and one for the Internet www.internet.com
>
> If a user accesses www.intranet.com/test, the webapp should be allowed to
> run, but if the user accesses www.internet.com/test, the access should be
> blocked.
>
> I have found that through
>
> <Valve className="org.apache.catalina.valves.RemoteAddrValve" ...
>
> I can define for which client IP Addresses the access should be allowed, but
> it would be much better for my purposes to make the decision to grant access
> or not based on the URL used.
>
> Thank you,
> dsc
> --
> View this message in context: http://www.nabble.com/Denying-access-to-a-webapp-when-accessing-it-through-a-specific-DNS-name-or-IP-Address-tp17492267p17492267.html
> Sent from the Tomcat - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org