Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 9475 invoked by uid 500); 20 Apr 2001 17:17:40 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: tomcat-user@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 9175 invoked from network); 20 Apr 2001 17:17:33 -0000 Received: from mail-oak-1.pilot.net (HELO mail01-oak.pilot.net) (198.232.147.16) by h31.sny.collab.net with SMTP; 20 Apr 2001 17:17:33 -0000 Received: from pfcwss02a.providian.com (unknown-148.pilot.net [206.189.47.148] (may be forged)) by mail01-oak.pilot.net with SMTP id KAA19643 for ; Fri, 20 Apr 2001 10:17:32 -0700 (PDT) From: Jason_Henriksen@providian.com Received: from 161.192.48.164 by pfcwss02a.providian.com with ESMTP ( Tumbleweed MMS SMTP Relay (MMS v4.7)); Fri, 20 Apr 2001 10:16:28 -0700 X-Server-Uuid: b52a0787-3e42-11d1-9534-00805fb2a7a9 Subject: Re: other session visible To: tomcat-user@jakarta.apache.org Date: Fri, 20 Apr 2001 10:17:21 -0700 Message-ID: X-MIMETrack: Serialize by Router on NASMTP01/USVR/Providian(Release 5.0.6a |January 17, 2001) at 04/20/2001 10:17:47 AM MIME-Version: 1.0 X-WSS-ID: 16FEB1611033610-01-04 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N My company was using gnuJSP and mod_jserv back in the day and we ran into a problem very similar to this. We swore up and down at the java code but could never find anything wrong with it. The problem was doubly irritating because we could not reproduce it in our development environment. It only occured in the field during demos and such. The real problem was proxy servers. If you are not very careful with your HTTP directives you'll find that a proxy server sees a request for: www.yourcompany.com/highlyDynamicJSP.jsp But the proxy server doesn't see a ? in the request so it assumes the request is static even though it isn't. The first user's request gets cached and the second user to make a request gets the first users data! I have sample code at home with the specifics of how we defated this. If people are curious I'll post it here. The main thing is to use HTTP headers to ensure that a proxy will never cache your pages. We put the 'no cache' stuff into a jsp snippet and included that snippet on every page. Our problem evaportated. Let me know if you want the specific source code, Jason Henriksen ------------------------------------------------------------------------------ Warning : The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to this message and then delete it from your computer. All e-mail sent to this address will be received by the Providian Financial corporate e-mail system and is subject to archiving and review by someone other than the recipient. ==============================================================================