Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 73814 invoked from network); 19 Jun 2003 13:49:51 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 19 Jun 2003 13:49:51 -0000 Received: (qmail 23300 invoked by uid 97); 19 Jun 2003 13:52:11 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@nagoya.betaversion.org Received: (qmail 23293 invoked from network); 19 Jun 2003 13:52:10 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 19 Jun 2003 13:52:10 -0000 Received: (qmail 69896 invoked by uid 500); 19 Jun 2003 13:49:04 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 69870 invoked from network); 19 Jun 2003 13:49:03 -0000 Received: from unknown (HELO warhawk.mpi.com) (63.244.250.133) by daedalus.apache.org with SMTP; 19 Jun 2003 13:49:03 -0000 Received: from lightning.mpi.com (lightning.mpi.com [63.244.252.11]) by warhawk.mpi.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h5JDn1601234 for ; Thu, 19 Jun 2003 09:49:01 -0400 (EDT) Received: from US-VS1.corp.mpi.com (us-be2.corp.mpi.com [199.93.195.21]) by lightning.mpi.com (Switch-3.0.4/Switch-3.0.0) with ESMTP id h5JDmio0022845 for ; Thu, 19 Jun 2003 09:49:03 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Advantages to putting Apache as front end to Tomcat Date: Thu, 19 Jun 2003 09:49:02 -0400 Message-ID: <9C5166762F311146951505C6790A9CF8A6E72F@US-VS1.corp.mpi.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Advantages to putting Apache as front end to Tomcat Thread-Index: AcM2Z7P3eaP5i9/VSwO0qiC7fE8TFwAAcHvQ From: "Shapira, Yoav" To: "Tomcat Users List" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Howdy, You can do CGI in tomcat-standalone: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/cgi-howto.html However, seeing as how CGI is an area where security is a big risk, I'= d rather delegate that to Apache. Yoav Shapira Millennium ChemInformatics >-----Original Message----- >From: Tim Shaw [mailto:tim@everserve.co.uk] >Sent: Thursday, June 19, 2003 9:39 AM >To: Tomcat Users List >Subject: Re: Advantages to putting Apache as front end to Tomcat > >Additional question if I may ... > >CGI? > >Reason : A previous Admin system was CGI-perl based. I have used TC t= o >do the stuff I do ... but we still need the previous bits. We're abou= t >to integrate, and I have taken it on 'faith' that we can just 'mix th= e 2 >together' - others know Apache well. > >I thought I'd piggyback on this question 'cos it seemed relevant - sorry. > >tim > >Collins, Jim wrote: >> One other point I would like to add is running on port 80. If you u= se >apache >> as soon as the server has started it can switch to another role whi= ch you >> can't do with Tomcat. >> >> -----Original Message----- >> From: Shapira, Yoav [mailto:yoav.shapira@mpi.com] >> Sent: 19 June 2003 14:07 >> To: Tomcat Users List >> Subject: RE: Advantages to putting Apache as front end to Tomcat >> >> >> >> Howdy, >> Apache is the best HTTP web server out there, I'd say. That's a >> sweeping statement that covers: >> - Configurability: you can configure pretty much anything any which= way >> - Stability: no other HTTP server is hit as hard / as much as Apach= e >> httpd, no other HTTP server is expected to stay up as long >> - Security: Apache is extremely well tested for security, constantl= y >> being analyzed by hackers, pros, etc. >> - Speed: for just serving static HTML content, Apache is as good as= they >> come IMHO >> >> Disadvangtes of Apache/Tomcat versus Tomcat-standalone include: >> - Increased configuration difficulty >> - Increased number of services (2 instead of 1) that need to be >> monitored, started, etc. >> - Increased difficulty of debugging problems >> >> Both Apache and Tomcat can do SSL/HTTPS by themselves. Both can do= >> virtual hosting by themselves. Apache is at least as good, possibl= y >> better, than tomcat at virtual hosting. >> >> This topic has been discussed at length, so I would usually say jus= t >> search the archives. However, I think a lot of people still have this >> conception that tomcat sucks at static content (which it doesn't) a= nd >> that all serious applications use apache as a front-end (which they= >> don't). I personally tend to have an operational view of things, a= nd >> have found tomcat-standalone (with a security manager and a tight >> security policy) to be sufficient for my real-world needs. >> >> I'm sure other people will disagree ;) But it's nice to have choices. >> If nothing else, you can always start with tomcat standalone, and i= f you >> run into something you can't do, add Apache. >> >> Yoav Shapira >> Millennium ChemInformatics >> >> >> >>>-----Original Message----- >>>From: Jeremy Nix [mailto:Jeremy.Nix@sfsltd.com] >>>Sent: Thursday, June 19, 2003 8:48 AM >>>To: tomcat-user@jakarta.apache.org >>>Subject: Advantages to putting Apache as front end to Tomcat >>> >>>What are the advantages/disadvantages to using Apache as the http >> >> server >> >>>sending all jsp/servlet related traffic to Tomcat for processing, o= r >>>using Tomcat stand alone? Other factors...I need to run SSL, and t= o >>>support multiple virtual hosts. >>> >>>_________________ >>>Jeremy Nix >>>Senior Application Developer >>>Southwest Financial Ltd. >>>Jeremy.Nix@sfsltd.com >>>(513) 621-6699 ext 1158 >> >> >> >> >> >> This e-mail, including any attachments, is a confidential business >> communication, and may contain information that is confidential, >proprietary >> and/or privileged. This e-mail is intended only for the individual(s) to >> whom it is addressed, and may not be saved, copied, printed, disclosed or >> used by anyone else. If you are not the(an) intended recipient, please >> immediately delete this e-mail from your computer system and notify= the >> sender. Thank you. >> >> >> -------------------------------------------------------------------= -- >> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org >> For additional commands, e-mail: tomcat-user-help@jakarta.apache.or= g >> >> >> PLEASE READ: The information contained in this email is confidentia= l >> and intended for the named recipient(s) only. If you are not an intended >> recipient of this email you must not copy, distribute or take any >> further action in reliance on it and you should delete it and notif= y the >> sender immediately. Email is not a secure method of communication a= nd >> Nomura International plc cannot accept responsibility for the accuracy >> or completeness of this message or any attachment(s). Please examin= e this >> email for virus infection, for which Nomura International plc accep= ts >> no responsibility. If verification of this email is sought then please >> request a hard copy. Unless otherwise stated any views or opinions >> presented are solely those of the author and do not represent those= of >> Nomura International plc. This email is intended for informational >> purposes only and is not a solicitation or offer to buy or sell >> securities or related financial instruments. Nomura International p= lc is >> regulated by the Financial Services Authority and is a member of th= e >> London Stock Exchange. >> >> >> >> -------------------------------------------------------------------= -- >> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org >> For additional commands, e-mail: tomcat-user-help@jakarta.apache.or= g >> > > > >---------------------------------------------------------------------= >To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org >For additional commands, e-mail: tomcat-user-help@jakarta.apache.org This e-mail, including any attachments, is a confidential business com= munication, and may contain information that is confidential, propriet= ary and/or privileged. This e-mail is intended only for the individua= l(s) to whom it is addressed, and may not be saved, copied, printed, d= isclosed or used by anyone else. If you are not the(an) intended reci= pient, please immediately delete this e-mail from your computer system= and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org