Re: Multiple paths to one application
actually the performance is better as you have control over what is being accessed, who is accessing and you dont have to play games with external http servers such as IIS / Apache M- This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents - Original Message - From: "Caldarale, Charles R" <[EMAIL PROTECTED]> To: "Tomcat Users List" Sent: Thursday, November 02, 2006 10:31 AM Subject: RE: Multiple paths to one application > From: Peter Neu [mailto:[EMAIL PROTECTED] > Subject: AW: Multiple paths to one application > > My problem is that I have parts of my application which are > restricted and I just want to filter the path requests with > the httpd server which sits in front of tomcat so that I > don't to configure any additional realms. For Tomcat, a realm is a collection of authentication credentials and the necessary logic to manipulate them - it's not an access control mechanism. For that, you use path-based declarations in your app's web.xml, as defined in section 12 of the Servlet spec. You don't need multiple realms for controlling access to different parts of an application. What are you using httpd for? If it's just for delivering static content, consider simplifying your life by getting rid of it and using Tomcat standalone. Performance is pretty much equivalent, these days. - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multiple paths to one application
> From: Peter Neu [mailto:[EMAIL PROTECTED] > Subject: AW: Multiple paths to one application > > My problem is that I have parts of my application which are > restricted and I just want to filter the path requests with > the httpd server which sits in front of tomcat so that I > don't to configure any additional realms. For Tomcat, a realm is a collection of authentication credentials and the necessary logic to manipulate them - it's not an access control mechanism. For that, you use path-based declarations in your app's web.xml, as defined in section 12 of the Servlet spec. You don't need multiple realms for controlling access to different parts of an application. What are you using httpd for? If it's just for delivering static content, consider simplifying your life by getting rid of it and using Tomcat standalone. Performance is pretty much equivalent, these days. - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: AW: Multiple paths to one application
Yes, I know this reaction but what are you gonna do when you are told Put user authentication in the DMZ, filter on an XOR basis between ip address and password? I did not find any better way. Besides how is it possible to connect to an port in the intranet which is closed and only open for an fixed ip address? Pete > -Ursprüngliche Nachricht- > Von: Andrew Miehs [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 2. November 2006 16:09 > An: Tomcat Users List > Betreff: Re: AW: Multiple paths to one application > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I hope that this is not really the reason why you want two paths to > the application? > > Tomcat has user authentication built in!? Why not use it?! Otherwise, > some smart user is > going to have the idea of connecting directly to your tomcat instance... > > If you have 'two' copies of the same web app, you may also end up > with other side-effects, depending on how the thing works > ... Two copies using the same database, when they each believe that > they are the only one connected! :-) > > > Andrew > > > On 02/11/2006, at 4:01 PM, Peter Neu wrote: > > > This means when I configure it like this it makes no difference to > > just > > deploying the same application twice with different paths, right? > > > > My problem is that I have parts of my application which are > > restricted and > > I just want to filter the path requests with the httpd server which > > sits > > in front of tomcat so that I don't to configure any additional realms. > > > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.1 (Darwin) > > iD8DBQFFSgoCW126qUNSzvURAn0uAJ9M8hRTpOCxPE+z7NOhho8tdVA39wCcDWpn > Cfj3u/04QUinjCoTLAYc6FU= > =jcI6 > -END PGP SIGNATURE- > > - > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: Multiple paths to one application
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I hope that this is not really the reason why you want two paths to the application? Tomcat has user authentication built in!? Why not use it?! Otherwise, some smart user is going to have the idea of connecting directly to your tomcat instance... If you have 'two' copies of the same web app, you may also end up with other side-effects, depending on how the thing works ... Two copies using the same database, when they each believe that they are the only one connected! :-) Andrew On 02/11/2006, at 4:01 PM, Peter Neu wrote: This means when I configure it like this it makes no difference to just deploying the same application twice with different paths, right? My problem is that I have parts of my application which are restricted and I just want to filter the path requests with the httpd server which sits in front of tomcat so that I don't to configure any additional realms. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFSgoCW126qUNSzvURAn0uAJ9M8hRTpOCxPE+z7NOhho8tdVA39wCcDWpn Cfj3u/04QUinjCoTLAYc6FU= =jcI6 -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Multiple paths to one application
This means when I configure it like this it makes no difference to just deploying the same application twice with different paths, right? My problem is that I have parts of my application which are restricted and I just want to filter the path requests with the httpd server which sits in front of tomcat so that I don't to configure any additional realms. -Pete > -Ursprüngliche Nachricht- > Von: Caldarale, Charles R [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 2. November 2006 15:27 > An: Tomcat Users List > Betreff: RE: Multiple paths to one application > > > From: Andrew Miehs [mailto:[EMAIL PROTECTED] > > Subject: Re: Multiple paths to one application > > > > Doesn't this only work if your application replaces the 'ROOT' > > application? > > Correct. > > If you want two names for the same app, you could place an additional > element in conf/[engine]/[host]/[app2name].xml, with a docBase > attribute pointing to the app to be aliased. This actually gets you two > deployments of the same app, so singletons and static fields won't be > shared across them. That may or may not suffice. > > - 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multiple paths to one application
> From: Andrew Miehs [mailto:[EMAIL PROTECTED] > Subject: Re: Multiple paths to one application > > Doesn't this only work if your application replaces the 'ROOT' > application? Correct. If you want two names for the same app, you could place an additional element in conf/[engine]/[host]/[app2name].xml, with a docBase attribute pointing to the app to be aliased. This actually gets you two deployments of the same app, so singletons and static fields won't be shared across them. That may or may not suffice. - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple paths to one application
you are right. you still have to include the webapps folder in your path. therefore it would work this way: localhost/myapp/path1/servlet1 localhost/myapp/path2/servlet2 i guess you had to replace the root app to have just / as your app folder... (just as you said) --stephan Andrew Miehs wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Doesn't this only work if your application replaces the 'ROOT' application? Andrew On 02/11/2006, at 9:56 AM, Stephan Schöffel wrote: if you map them to one app in your web.xml you can have different paths link to one app. like: MyServlet my.Servlet MyServlet /path1/servlet1 MyServlet /path2/servlet2 both links would map to MyServlet ie my.Servlet.class -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFSbbPW126qUNSzvURAn4qAKCUxRJ5gzOEVTINFsLzggswi6n1VACfc+mE GHpg8SLtzz0o5x4op7JhmNg= =4vxd -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple paths to one application
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Doesn't this only work if your application replaces the 'ROOT' application? Andrew On 02/11/2006, at 9:56 AM, Stephan Schöffel wrote: if you map them to one app in your web.xml you can have different paths link to one app. like: MyServlet my.Servlet MyServlet /path1/servlet1 MyServlet /path2/servlet2 both links would map to MyServlet ie my.Servlet.class -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFSbbPW126qUNSzvURAn4qAKCUxRJ5gzOEVTINFsLzggswi6n1VACfc+mE GHpg8SLtzz0o5x4op7JhmNg= =4vxd -END PGP SIGNATURE- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple paths to one application
if you map them to one app in your web.xml you can have different paths link to one app. like: MyServlet my.Servlet MyServlet /path1/servlet1 MyServlet /path2/servlet2 both links would map to MyServlet ie my.Servlet.class Peter Neu wrote: Hello, is here a way to have multiple paths configured for one apps? Like : Localhost/path1/servlet1 Localhost/path2/servlet2 Cheers, Pete - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Multiple paths to one application
Hello, is here a way to have multiple paths configured for one apps? Like : Localhost/path1/servlet1 Localhost/path2/servlet2 Cheers, Pete - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
