On Sep 5, 2008, at 7:53 AM, Yung-Luen Lan wrote:
Uh, to be more pricisely, my problem is not because WO won't parse
empty cookie properly.
My problem is, cookie containing wosid and woinst will be deleted
after quitting browser. Hence, there's no way to implement function
like "login automatic
Is there any way to keep session cookie after quit browsers?
This isn't really a reliable way to implement this feature anyway,
though. You would need to make your session lifetime way to long for
this to be useful. A better way would be for you app to set a custom
auth token cookie (that
Uh, to be more pricisely, my problem is not because WO won't parse
empty cookie properly.
My problem is, cookie containing wosid and woinst will be deleted
after quitting browser. Hence, there's no way to implement function
like "login automatically."
Digging into this problem, I found that my se
Hello Yung-Luen;
I think these empty cookies will parse in WO 5.4.2 now, but the
application server will log an error each time which is a bit
annoying. I get my error log lines emailed to me so it was actually
very annoying for a short while there! For this reason, I left that
code (ma
Hi,
Is this issue fixed in 5.4.2? I still encountered this problem (Not
only Safari 3, but also FireFox 3 delete my cookie on quit) in 5.4.2.
However, with Andrew's code inside my WOApplication.createRequest(), I
still got the same problem.
What could be wrong in my code?
I rewrote some lin
Hello Ryan;
I stuck this...
// [apl 18.feb.2008]
// WebObjects 5.4.1 has a problem dealing with cookies that have their
value as
// an empty string. This little block of code should be able to
remove those
// such that they no longer pose a problem for the WO parser. This
MUST BE
// rem
I just tried this and also had the same problem under safari. It
would appear that safari is ignoring the max-age attribute, and
treating the cookie as a session cookie. I've filed a radar on the
safari team. Firefox does treat the cookie properly. *sigh*
5.4.2 is not a released product
Is 5.4.2 available? I only see 5.4.1.
I've tried to use timeout, but Safari still deletes my cookies on exit.
Michael
On Mar 3, 2008, at 5:50 PM, Ryan Klems wrote:
This is a bug, fixed in 5.4.2. As a workaround, you could use the
timeout instead of the expiration date (max-age vs. expires
This is a bug, fixed in 5.4.2. As a workaround, you could use the
timeout instead of the expiration date (max-age vs. expires
attribute). (I know this isn't great for existing code).
-Ryan
On Mar 3, 2008, at 11:54 AM, Chuck Hill wrote:
On Mar 3, 2008, at 10:50 AM, Michael Kondratov wrot
On Mar 3, 2008, at 10:50 AM, Michael Kondratov wrote:
Looks like Wo 5.4 or 5.4.1 (not sure)
[2008-3-3 18:24:21 EST] WebObjects version = 5.4
Safari Version 3.0.4 (5523.15)
What's the current proper way of doing cookies in WO? :)
Use WO 5.3.3. :-)
Check the RFC: http://www.ietf.org/rfc/rf
Looks like Wo 5.4 or 5.4.1 (not sure)
[2008-3-3 18:24:21 EST] WebObjects version = 5.4
Safari Version 3.0.4 (5523.15)
What's the current proper way of doing cookies in WO? :)
Michael
On Mar 3, 2008, at 1:45 PM, Chuck Hill wrote:
Which version of WO? Have you updated recently? Have you upda
Which version of WO? Have you updated recently? Have you updated
Safari recently? Have you checked the expires date format in the
Cookie RFC? Is WO generating the wrong format, or is this a Safari bug?
Chuck
On Mar 3, 2008, at 10:39 AM, Michael Kondratov wrote:
For some unknown reason s
For some unknown reason safari no longer properly parses my cookie
generated by WOCookie.
The cookies always expire when browser closes. When I look at safari's
properties, my cookies have no expiration dates.
My code:
String hostName = ".aspireauctions.com";
String path = "/";
NSTimestamp c
13 matches
Mail list logo
