On 19 Sep 2018, at 23:54, Jesse Tayler wrote:
> Maybe we should make note in the wiki pages?
>
> There was very little about WOCookie, but a simple listing of a line that
> works could help I’d imagine…
Definitely. Do it.
--
Paul Hoadley
https://logicsquad.net/
https://www.
I just used what you threw me and right off it just worked as planned.
Basically the test is to log in locally, quite browser and return and if you’re
still logged in? Then it worked.
Maybe we should make note in the wiki pages?
There was very little about WOCookie, but a simple listing of a
> On Sep 17, 2018, at 2:52 PM, Klaus Berkling wrote:
>>>
>>>
>>>
>>> On Sep 17, 2018, at 9:50 AM, Jesse Tayler wrote:
>>>
>>> I think I’ve tried everything I could think of —
>>>
>>> Do you have say, a login cookie that
t;
>> 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);
>
> On Sep 17, 2018, at 9:50 AM, Jesse Tayler <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(userGUI
PM, Theodore Petrosky 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);
> (r
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 vari
Thank you.
On Feb 4, 2010, at 2:38 PM, Chuck Hill wrote:
>
> On Feb 4, 2010, at 4:30 PM, Johnny Miller wrote:
>
>> Hi,
>>
>> If I set a WOCookie when the user visits http://www.example.com which saves
>> some state how do I retrieve that info if for some reas
On Feb 4, 2010, at 4:30 PM, Johnny Miller wrote:
Hi,
If I set a WOCookie when the user visits http://www.example.com
which saves some state how do I retrieve that info if for some
reason they return to the site on http://example.com
I tried setting the domain when the WOCookie gets
Hi,
If I set a WOCookie when the user visits http://www.example.com which saves
some state how do I retrieve that info if for some reason they return to the
site on http://example.com
I tried setting the domain when the WOCookie gets created to
http://www.example.com but that didn't se
Hi there,
I've subclassed WOResponse (ok ERXResponse) in order to add a rewrite
hook for the setting of the cookies' domain (which by default is
always empty). That's the easy part.
The interesting thing is that when the browser receives the cookies
they've all been preceded by a dot ('.'
19, 2009, at 1:18 AM, Amedeo Mantica wrote:
Hello,
I have just discovered that is impossible to set a WOCookie in the
meanwhile of an AjaxRequest
is a bug or a tecnical limitation?
I'd say technical limitation. Returning some JavaScript to set the
cookie is probably the easies
On Feb 19, 2009, at 1:18 AM, Amedeo Mantica wrote:
Hello,
I have just discovered that is impossible to set a WOCookie in the
meanwhile of an AjaxRequest
is a bug or a tecnical limitation?
I'd say technical limitation. Returning some JavaScript to set the
cookie is probabl
Hello,
I have just discovered that is impossible to set a WOCookie in the
meanwhile of an AjaxRequest
is a bug or a tecnical limitation?
Regards
Amedeo
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list
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
hael Kondratov wrote:
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&qu
ses 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 currentTime = n
g?
Chuck
On Mar 3, 2008, at 10:39 AM, Michael Kondratov wrote:
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:
ating 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 safari no longer properly parses my cookie
generated by WOCookie.
The cookies always expire when browser closes. When I look at
safari's properties,
ed 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 currentTime = new NSTimes
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 = "/";
NSTi
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 = &
Hello Joe;
I have just worked around the problem you have mentioned by parsing-
and-dumping empty cookies in my WOApplication.createRequest(..)
override. It's a crude patch until the next WO version, but it seems
to remove the problem.
cheers.
The cookie issue unfortunately missed that u
The easiest way to customize cookies behavior is to have you own
subclass of WOResponse. There quite a few hooks you can use to
customize the behavior.
Pierre
--
Pierre Frisch
[EMAIL PROTECTED]
On Jan 11, 2008, at 9:59, Joe Moreno wrote:
Pierre,
Thanks for clearing up the cookie
Pierre,
Thanks for clearing up the cookie and time zone issue.
I didn't know the problem with the time zone was a WO bug, I thought
it was an Eclipse bug.
Also, I've tried several different ways to delete the wosid cookie
when I'm terminating a session without any luck.
Can you r
On 11/01/2008, at 5:35 PM, Joe Moreno wrote:
Hi All,
I just upgraded from Tiger client to Leopard and I've noticed two
issues.
First, the Eclipse Console correctly reports the time zone as PST,
but the actual time digits are GMT. Am I missing something? I'm
running Eclipse 3.3.1.1 and
Hi Joe,
Both are known bugs.
The GMT/PST bug will be fixed in the next update of WO.
The cookie issue unfortunately missed that update and will have to
wait for the next one. The issue is that the cookie parsing is too
strict and consider the empty value as a mistake so it trips on
wosid=
Hi All,
I just upgraded from Tiger client to Leopard and I've noticed two
issues.
First, the Eclipse Console correctly reports the time zone as PST,
but the actual time digits are GMT. Am I missing something? I'm
running Eclipse 3.3.1.1 and WOLips 3.3.4574.
Second, I keep getting An
can store other information in a cookie:
- WO can manipulate cookies through the WOCookie class.
See http://developer.apple.com/documentation/Webobjects/Reference/API/
com/webobjects/appserver/WOCookie.html
If you are asking whether you can detect if cookies are enabled on
the client browser
Hello,
Is there a way to detect if the cookies are enabled with WebObjects?
Thank you.
Bruno.
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update y
35 matches
Mail list logo
