From tomcat-user-return-88372-apmail-jakarta-tomcat-user-archive=jakarta.apache.org@jakarta.apache.org Wed Jan 07 18:31:01 2004 Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 41316 invoked from network); 7 Jan 2004 18:31:01 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 7 Jan 2004 18:31:01 -0000 Received: (qmail 71114 invoked by uid 500); 7 Jan 2004 18:30:33 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 71098 invoked by uid 500); 7 Jan 2004 18:30:33 -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 71079 invoked from network); 7 Jan 2004 18:30:33 -0000 Received: from unknown (HELO corpusic3.corp.emc.com) (168.159.2.32) by daedalus.apache.org with SMTP; 7 Jan 2004 18:30:33 -0000 Received: by corpusic3.corp.emc.com with Internet Mail Service (5.5.2653.19) id ; Wed, 7 Jan 2004 13:30:36 -0500 Message-ID: <54E90801719C734E9969C98D40DE1E8640C881@corpusmx2.corp.emc.com> From: "Talley, Angelina" To: "'tomcat-user@jakarta.apache.org'" Subject: Making index.jsp work as welcome page after upgrade Date: Wed, 7 Jan 2004 13:30:35 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3D54C.5716D210" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N ------_=_NextPart_001_01C3D54C.5716D210 Content-Type: text/plain Hello! I just upgraded a web application from Tomcat 4.0.6/mod_jk 1.2.5 to Tomcat 4.1.29/mod_jk2 2.0.2 (built myself), both on Apache 1.3.27 on Linux. Our webapp runs as the ROOT context (files are in $TOMCAT_HOME/webapps/ROOT). We have precompiled the JSP pages for 4.1.29, but did not do that in 4.0.6. On the old setup, to get to our application all you had to do was type https://myserver and you'd get index.jsp by default. Now, if you type the URL like that you get a directory listing. You have to explicitly put index.jsp in the URL to get to it. If you do that, the entire web app works just fine. Is there some new configuration item I need to tweak here? I tried adding a segment for welcome-file-list to my web.xml: index.jsp But it still doesn't work. Any other suggestions would be greatly appreciated. I figured perhaps my workers2.properties was messed up, so I'll put a sample of that below. I made almost no changes at all to server.xml except to add tomcatAuthentication="false" for the Coyote connector and to comment out the connector on port 8080. I should note that if run as Tomcat standalone (without Apache) on Windows (haven't tried Linux because of our authentication setup), it works perfectly. >From workers2.properties: # # IP socket channel # [channel.socket:localhost:8009] port=8009 host=127.0.0.1 # # define the ajp13 worker # [ajp13:localhost:8009] channel=channel.socket:localhost:8009 # # Uri mapping - jsp files only # [uri:/*.jsp] group=ajp13:localhost:8009 # # Uri mapping - Struts stuff # [uri:/action/*] group=ajp13:localhost:8009 # # Uri mapping - all servlets in servlets directory # [uri:/servlets/*] group=ajp13:localhost:8009 >From server.xml: Entire jk2.properties: # # Socket configuration # handler.list=request,container,channelSocket # # socket configuration # channelSocket.port=8009 channelSocket.address=127.0.0.1 channelSocket.maxPort=port+10 Thanks! -Angelina Talley ------_=_NextPart_001_01C3D54C.5716D210--