Klaus!

You’ve done it — ok, I guess somehow I did NOT try that…sigh…

Well, thanks - that seems to do the trick



> On Sep 17, 2018, at 2:52 PM, Klaus Berkling <webobje...@berkling.us> wrote:
> 
> 
> 
>> On Sep 17, 2018, at 9:50 AM, Jesse Tayler <jtay...@oeinc.com 
>> <mailto:jtay...@oeinc.com>> wrote:
>> 
>> I think I’ve tried everything I could think of —
>> 
>> Do you have say, a login cookie that lasts after browser restart?
>> 
> 
> This is mine.
> 
> WOCookie cookie = new WOCookie(userGUIDCookieKey, guid, "/", null, 2592000, 
> false);
> 
> I recall having an issue with setting it to secure. I think -1 didn’t work 
> but it’s been a long time.
> 
> 
>> Paste in your initializer and I’ll try it —
>> 
>> I read something about setting the setExpires specifically to nil  and tried 
>> it any number of ways.
>> 
>> 
>> 
>>> On Sep 17, 2018, at 12:47 PM, Theodore Petrosky <tedp...@yahoo.com 
>>> <mailto:tedp...@yahoo.com>> wrote:
>>> 
>>> Jesse,
>>> 
>>> I see that there are overloaded constructors. maybe it doesn’t like being 
>>> set once it is created!
>>> 
>>> 
>>> WOCookie cookie = new WOCookie(“USER_ID", userIdentifierCode, "/", null, 
>>> -1, null, true);
>>> (remove the setExpires)
>>> 
>>> public WOCookie(final String name, final String value, final String path, 
>>> final String domain, final NSTimestamp expires, final boolean isSecure) {
>>>             this(name, value, path, domain, expires, isSecure, false);
>>>     }
>>> 
>>> just curious if setting the expires in the constructor does anything 
>>> different!
>>> 
>>>     
>>> 
>>>> On Sep 17, 2018, at 11:44 AM, Jesse Tayler <jtay...@oeinc.com 
>>>> <mailto:jtay...@oeinc.com>> wrote:
>>>> 
>>>> Hi All
>>>> 
>>>> I’ve tried fussing around with various arguments but for whatever reason 
>>>> my WOCookie always dies when the browser restarts?
>>>> 
>>>>    WOCookie cookie = new WOCookie(“USER_ID", userIdentifierCode, "/", 
>>>> null, -1, true);
>>>>    cookie.setExpires(null);
>>>> 
>>>> 
>>>> I’ve tried various expires and timeout combinations can anyone say what it 
>>>> is that I’m doing wrong ?
>>>> 
>>>> Seems DISTANT FUTURE is a common need, so I’m confused!
>>>> 
>>>> thanks
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Do not post admin requests to the list. They will be ignored.
>>>> Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com 
>>>> <mailto:Webobjects-dev@lists.apple.com>)
>>>> Help/Unsubscribe/Update your Subscription:
>>>> https://lists.apple.com/mailman/options/webobjects-dev/tedpet5%40yahoo.com 
>>>> <https://lists.apple.com/mailman/options/webobjects-dev/tedpet5%40yahoo.com>
>>>> 
>>>> This email sent to tedp...@yahoo.com <mailto:tedp...@yahoo.com>
>>> 
>> 
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com 
>> <mailto:Webobjects-dev@lists.apple.com>)
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/webobjects-dev/webobjects%40berkling.us
>>  
>> <https://lists.apple.com/mailman/options/webobjects-dev/webobjects%40berkling.us>
>> 
>> This email sent to webobje...@berkling.us <mailto:webobje...@berkling.us>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com 
> <mailto:Webobjects-dev@lists.apple.com>)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/jtayler%40oeinc.com 
> <https://lists.apple.com/mailman/options/webobjects-dev/jtayler%40oeinc.com>
> 
> This email sent to jtay...@oeinc.com <mailto:jtay...@oeinc.com>
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to