Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Message-ID: <3EF1E5DF.3050403@everserve.co.uk>
Date: Thu, 19 Jun 2003 17:33:35 +0100
From: Tim Shaw <tim@everserve.co.uk>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.0.1) Gecko/20020823 Netscape/7.0
MIME-Version: 1.0
To: Tomcat Users List <tomcat-user@jakarta.apache.org>
Subject: Re: Advantages to putting Apache as front end to Tomcat
References: <9C5166762F311146951505C6790A9CF8A6E72F@US-VS1.corp.mpi.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Thanks - 'fraid I was being lazy (didn't check beforehand) but it was 
not high on my priority list.

Shapira, Yoav wrote:
> 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 to
>>do the stuff I do ... but we still need the previous bits. We're about
>>to integrate, and I have taken it on 'faith' that we can just 'mix the
> 
> 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 use
>>
>>apache
>>
>>>as soon as the server has started it can switch to another role which
>>
> 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 Apache
>>>httpd, no other HTTP server is expected to stay up as long
>>>- Security: Apache is extremely well tested for security, constantly
>>>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, possibly
>>>better, than tomcat at virtual hosting.
>>>
>>>This topic has been discussed at length, so I would usually say just
>>>search the archives.  However, I think a lot of people still have
>>
> this
> 
>>>conception that tomcat sucks at static content (which it doesn't) and
>>>that all serious applications use apache as a front-end (which they
>>>don't).  I personally tend to have an operational view of things, and
>>>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 if
>>
> 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, or
>>>>using Tomcat stand alone?  Other factors...I need to run SSL, and to
>>>>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.org
>>>
>>>
>>>PLEASE READ: The information contained in this email is confidential
>>>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 notify
>>
> the
> 
>>>sender immediately. Email is not a secure method of communication and
>>>Nomura International plc cannot accept responsibility for the
>>
> accuracy
> 
>>>or completeness of this message or any attachment(s). Please examine
>>
> this
> 
>>>email for virus infection, for which Nomura International plc accepts
>>>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 plc
>>
> is
> 
>>>regulated by the Financial Services Authority and is a member of the
>>>London Stock Exchange.
>>>
>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>>>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>>>
>>
>>
>>
>>---------------------------------------------------------------------
>>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 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.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org