On Fri, Mar 7, 2014 at 9:37 AM, Christopher Schultz <ch...@christopherschultz.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Leo, > > On 3/7/14, 10:44 AM, Leo Donahue wrote: >> Who uses more than one Service in their server.xml and why? I get >> that you can have multiple Connectors if you have multiple Service >> components but why use multiple connectors? > > You can already have multiple <Connector>s per <Service> but the > difference is that all Connectors in Service can access all web > applications in that Service. > >> Are there any docs on the use cases for these features? > > Let's say that you wanted to deploy a non-secure webapp (/open) and a > secure webapp (/secure). And let's say that you were terribly paranoid > about proper setup: you want to make sure that nobody can access your > /secure webapp without going through HTTPS. > > If you were to simply do this: > > <Service> > <Connector port="80" /><!-- let's just be brief --> > <Connector port="443" /> > <Host appBase="webapps" /> > </Service> > > ... then anyone could access either web application via http:// and > https://. (Of course, you'd set "CONFIDENTIAL" in your web.xml, but > remember, we're being paranoid, here). > > Instead, you can do this: > > <Service> > <Connector port="80" /><!-- let's just be brief --> > <Host appBase="insecure-webapps" /> > </Service> > <Service> > <Connector port="443" /> > <Host appBase="secure-webapps" /> > </Service> > > This way, anyone requesting http:///secure would get a 404. > > I'm sure you could come up with a real-world use-case for the above, <snip> It's good enough to get the wheels turning... Thanks.
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
