Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 58529 invoked from network); 6 Jun 2002 16:24:02 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 6 Jun 2002 16:24:02 -0000 Received: (qmail 4725 invoked by uid 97); 6 Jun 2002 16:23:44 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 4687 invoked by uid 97); 6 Jun 2002 16:23:43 -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 4675 invoked by uid 98); 6 Jun 2002 16:23:42 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: Apache 1.3, Tomcat 3.2.3 SSL woes X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Thu, 6 Jun 2002 10:23:29 -0600 Message-ID: <6B3DA9E253C1F345BD0706DE9871387503BB9D@ds9.petroleumplace.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Url rewrite thread-index: AcINcMknkmQSiHZeSkSFt+anB9oXwQAAMFngAACrtcA= From: "Noyce, Ben W." 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 Greetings everyone, We are running into some interesting scenarios with Apache 1.3, Tomcat = 3.2.3, and SSL. Hoping for some insight, we turn to you... Setting: We are running Apache 1.3 with mod_ssl on top of Linux Red Hat 7.+. = Tomcat 3.2.3 is configured without SSL support. Our mod_jk.so has been = compiled without EAPI. Problem: Intermittently during an Internet Explorer session, an SSL request will = return a 'Page not found' error. During a Netscape session, some SSL = form posts will result in the printing of an HTTP header on the web page = along with Hex displaced at certain points within the page. Question: What the heck is happening here? Everything was extremely happy until = the implementation of SSL. Since however, SSL requests randomly get = dropped or garbled - leading us to believe that this is a server = configuration issue. Are we correct in this belief? Anywhere that we = can turn? Any ideas? Humbly yours, BWN -- To unsubscribe, e-mail: For additional commands, e-mail: