Here is the solution:
Since no one found out...we had to do it ourselves. All of you Jrun users will
sooner or later face this bug (if you need cookies). After digging here and
there we found out that JRun has a bug with the setAge property. That's why
people faced problems with deleting cookies (setAge(0) to delete the cookie is
using the setAge which does not work in Jrun).
You just have to use the addCookie method of the HttpServletResponse with the
entire cookie string. Create the cookie with
Cookie cookie = new Cookie (name, cookieValue.toString());
The cookieValue has all the cookies you need with the whole cookie fields
(expires, path, domain etc.) separated by a comma (;). Then just call
response.addCookie(cookie) and voila...
It would have been just more normal for Jrun to fix the bug, but whatever...
Regards.
Arie Fishler wrote:
> Hi !
>
> I am using JRun Pro 2.3.1 Build 145 . I am facing a strange phenomenon
> while setting cookies. When I try to set the cookie for a longer age
> then a session (positive number for setAge) I don't succeed while
> working with a Netscape browser. The cookie is deleted when the browser
> is closed. When I turn on the option of warning before setting a cookie,
> I get the warning but with no expiry time. Trying to snif the HTTP data
> which passes I see that the expire time is all mixed up. The problem
> occurs ONLY in Netscape. Did anyone face that problem? What's the
> suggested workaround?
>
> Thanks.
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff JSP-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
