Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 16614 invoked from network); 8 Jul 2003 19:27:52 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 8 Jul 2003 19:27:52 -0000 Received: (qmail 25474 invoked by uid 97); 8 Jul 2003 19:30:22 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@nagoya.betaversion.org Received: (qmail 25467 invoked from network); 8 Jul 2003 19:30:21 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 8 Jul 2003 19:30:21 -0000 Received: (qmail 15135 invoked by uid 500); 8 Jul 2003 19:27:34 -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 15115 invoked from network); 8 Jul 2003 19:27:34 -0000 Received: from unknown (HELO laffrsdev.laf.resortquest.com) (12.147.92.50) by daedalus.apache.org with SMTP; 8 Jul 2003 19:27:34 -0000 Received: from markltp ([10.98.30.130]) by laffrsdev.laf.resortquest.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 8 Jul 2003 13:27:39 -0600 From: "Mark Miller" To: Subject: SSL and URL rewriting problem Date: Tue, 8 Jul 2003 13:27:21 -0600 Message-ID: <004001c34586$f3fe9d70$821e620a@markltp> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0041_01C34554.A9642D70" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-OriginalArrivalTime: 08 Jul 2003 19:27:39.0300 (UTC) FILETIME=[FE6D0E40:01C34586] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ------=_NextPart_000_0041_01C34554.A9642D70 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit I am working on a web application for which one form must be submitted via HTTPS (while the rest of the application uses HTTP). When that one form is submitted (and URL rewriting is used for session tracking), the URL is not encoded, and the session does not survive. I have done much googling, and there are several postings that this has been fixed as of Tomcat 4.0 (we are on 4.1.18). Can someone clear this up for me? If it cannot be done this way, is there some way to switch protocols and still track sessions? Thanks, Mark Miller ------=_NextPart_000_0041_01C34554.A9642D70--