Uma, Sorry for the delay. I went to bed early for a change.
Attachments don't survive. You will need to put it in the body of the email. List can you comment on if I am anywhere close on this or totally off my rocker. Thanks. Doug ----- Original Message ----- From: <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Monday, March 29, 2004 1:33 AM Subject: Re: Configuring Tomcat on different IP's > > > > > Doug, > Can you look at this server.xml file to see if I have done everything > correct? > > (See attached file: server.xml) > > Thank you, > Best Regards, > Uma > > > > "Parsons > Technical > Services" To > <parsonstechnical > @earthlink.net> "Tomcat Users List" > <[EMAIL PROTECTED]> > 03/29/2004 12:31 cc > PM > > > Please respond to > "Tomcat Users > List" Subject > <[EMAIL PROTECTED] Re: Configuring Tomcat on different > rta.apache.org> IP's > > > > > > > > > > > Okay to continue, > > In the Server element you can declare two services. In one service you > would > have the connector for the http and the context for your application. Note > unless someone can tell me how to control which service a context is > associate you will have to put your context in the server.xml. > > In the other sevice you will declare the https and the other context. > > Now for clarification I have NOT done this before and am basing it on what > I > read from the config documentaion. > > If you look in the server.xml file you will find the connector declaration > for the http. If you have NOT used the admin application, you will also > find > the connector for the https but it will be commented out <!-- --> . > > To try this first make a copy of the server.xml. > Next copy and paste the service section from start tag <service .... to > finish tag </service> and paste it right after the service finish tag. > In the second service tag you will need to change the name on the service > and maybe the engine. > Then comment out the http connector and uncomment the https connector. > Add the address= to each connector. > Add the context for your applications in the appropriate service. > > Restart tomcat and see what the logs say. > > Again, I have never done this. But the configuration docs say: > > Quote > The following components may be nested inside a Server element: > > Service - One or more service element. > GlobalNamingResources - Configure the JNDI global resources for the server. > Unquote > > So having two services is okay. > > Now can someone tell me which service an application will be associated > with > if you use the context.xml in the app? > > Give it a try and read up on the docs at: > > http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/server.html > > Good luck. > > Doug > > ----- Original Message ----- > From: "Parsons Technical Services" <[EMAIL PROTECTED]> > To: "Tomcat Users List" <[EMAIL PROTECTED]> > Sent: Monday, March 29, 2004 1:26 AM > Subject: Re: Configuring Tomcat on different IP's > > > > Clicked too fast. There is more to come... > > > > ----- Original Message ----- > > From: "Parsons Technical Services" <[EMAIL PROTECTED]> > > To: "Tomcat Users List" <[EMAIL PROTECTED]> > > Sent: Monday, March 29, 2004 1:19 AM > > Subject: Re: Configuring Tomcat on different IP's > > > > > > > Uma, > > > > > > I think this will do what you want. > > > > > > For each connector defined, one for http and one for https use the > address > > > attribute to specify the IP to listen on. > > > > > > So in the https connector use address="192.68.xxx.xx1" and Tomcat will > > > listen on 192.68.xxx.xx1 for only https request. > > > > > > On the http connector use address="192.68.xxx.xx2" and Tomcat will > listen > > > only for http request on 192.68.xxx.xx2 . > > > > > > Remember this affect all applications running on this instance of > Tomcat. > > > > > > See this for details: > > > > > > http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/http.html > > > > > > Doug > > > > > > > > > ----- Original Message ----- > > > From: <[EMAIL PROTECTED]> > > > To: "Tomcat Users List" <[EMAIL PROTECTED]> > > > Sent: Sunday, March 28, 2004 11:58 PM > > > Subject: Re: Configuring Tomcat on different IP's > > > > > > > > > > > > > > > > > > > > > > > > > > Doug, > > > > Thanks for the reply. It is just for security reasons out network > > > > administrator has planned to do. So, I need to configure as such. I > have > > > > made the settings in the code to see if the user is using http or > https > > > and > > > > block the user from using http. > > > > > > > > But there should be some way of doing this, right? > > > > > > > > Thank you, > > > > Best Regards, > > > > Uma > > > > > > > > > > > > > > > > > > > > "Parsons > > > > Technical > > > > Services" > > To > > > > <parsonstechnical > > > > @earthlink.net> "Tomcat Users List" > > > > > <[EMAIL PROTECTED]> > > > > 03/29/2004 11:23 > > cc > > > > AM > > > > > > > > > > > > Please respond to > > > > "Tomcat Users > > > > List" > > Subject > > > > <[EMAIL PROTECTED] Re: Configuring Tomcat on > > different > > > > rta.apache.org> IP's > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Uma, > > > > > > > > First don't take this wrong but I got to ask Why? > > > > > > > > Someone with more knowledge will have to chime in to say if this can > be > > > > done. But if the goal is to send all request for > http://www.mysite.com > > to > > > > https://www.mysite.com then Tomcat can do this for you. And without > two > > > > IPs. > > > > For details see; > > > > http://marc.theaimsgroup.com/?l=tomcat-user&m=104951559722619&w=2 > > > > > > > > If you have some special reason for the two IPs then, never mind.... > > > > > > > > Doug > > > > www.parsonstechnical.com > > > > > > > > > > > > ----- Original Message ----- > > > > From: <[EMAIL PROTECTED]> > > > > To: <[EMAIL PROTECTED]> > > > > Sent: Sunday, March 28, 2004 11:23 PM > > > > Subject: Configuring Tomcat on different IP's > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi, > > > > > My Tomcat 5.0.19 configuration is typical. I have got 2 IP > addresses > > > > > (202.200.xxx.xx1 and 202.200.xxx.xx2) which are pointing to 2 > internal > > > IP > > > > > addresses (192.68.xxx.xx1 and 192.68.xxx.xx2) > > > > > > > > > > I have registered one domain name (www.mysite.com). The entire site > > > > should > > > > > work only on https:// > > > > > > > > > > I need to configure this domain in such a way that the first IP > > address > > > > > (202.200.xxx.xx1) will have only one page(dummy jsp page that will > fwd > > > to > > > > > https home page of the site) and this IP address will accept only > 80 > > > > port. > > > > > > > > > > The second IP address (202.200.xxx.xx2) will server only 443 > requests. > > > > And > > > > > the pages that are accessed in https should not be accessed by http > > > > > protocol. > > > > > > > > > > I understand that I need to create 2 contexts and place the dummy > jsp > > > > page > > > > > in one context and the rest of the files in the 2nd context. > > > > > > > > > > But how do I configure that the first context should work only on > 80 > > and > > > > > the second context should work only on 443 port? > > > > > > > > > > Any help would be great. > > > > > > > > > > Thanks > > > > > Uma > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > ---------------------------------------------------------------------------- ---- > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
