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
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?
> -----Original Message-----
> From: dru-webware@... [mailto:dru-webware@...]
> Sent: Friday, June 14, 2002 5:14 PM
> To: webware-discuss@...
> 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 -
Webware-discuss mailing list
Get latest updates about Open Source Projects, Conferences and News.