- Tomcat 3.x implements HTTP 1.0 So in some cases you can get trouble, if the clients of your server uses some features of HTTP 1.1. (For example at least some versions of the acrobat reader plugin for IE use byte rage requests to get PDF files, which can lead into trouble) - Apache has possibly a more robust implementation of the HTTProtocol. - Apache has quite a lot of modules that have (afaik) no counterpart in tomcat. (e.g.: mod_rewrite) - Apache may be faster in serving static files In the long term I think pure tomcat will be the better alternative. But for that you have to wait for 4.x. > -----Urspr�ngliche Nachricht----- > Von: Tim McNerney [mailto:[EMAIL PROTECTED]] > Gesendet: Dienstag, 24. Oktober 2000 19:43 > An: [EMAIL PROTECTED] > Betreff: To use Apache or not <snip/> > I am trying to understand any disadvantages of using Tomcat directly, > without going through Apache. <snip/>
