It's entirely browser dependent. Try using expires instead of max-age
(expires was used in some http 1.0 implementations before max-age took
over in http 1.1). You need to write the raw headers for it, see
http://mrcoles.com/blog/cookies-max-age-vs-expires/.
Kalle
On Mon, Mar 26, 2012 at 4:38 AM, karthi <rathinasamy....@snovabits.net> wrote:
> Thank you for your reply,
>
> In javax.servlet also can't able to set the max age, if I set so then in the
> samsung galaxy nexus s mobile the cookies does not get write or saved
>
> In tapestry services cookies also worked now in the same device by removing
> the max age parameter like below:
>
> cookies.writeCookieValue("isUserLogin", "True");
>
> But in the devices which I have tested so far - Iphone, HTC, Samsung s2,
> Sony ericson & some other android models this cookie with max age is working
> perfectly no issues in those devices, this issue is only in the nexus s
> mobile.
>
> Now how can I set the max age for the cookies?
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Tapestry5-services-cookies-not-get-writes-in-samsung-galaxy-nexus-s-tp5591264p5594974.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
