It wouldn't be hard to modify Application.forward() so that it would copy cookies from the old response object to the new response object. But maybe it should be optional -- sometimes you might really want to discard the cookies.
How about adding an argument preserveCookies=0 which if set to 1 copies the cookies into the new response? Or should preserveCookies=1 be the default? - Geoff > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Friday, June 14, 2002 5:14 PM > To: [EMAIL PROTECTED] > Subject: [Webware-discuss] Re: Cookies > > > > One last tip, I ran into this. > > If you do set a cookie, make sure you don't forward the user > to another page. The cookie settings only get set if you > actually respond or redirect the user. When you forward, > a new response object is created and your cookie change > is lost. > > > > Thanks Luke & Geoff for the cookies tip. > > > > So what's the best way of getting to know when a client enters any > > page for the first time "per session" within the context. I would > > prefer to initiate the long-life cookie on a place outside a > > SitePage.py alike servlet. > > > > > > > > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
