WApplication::setCookie() Bug?

Added by Frank B over 1 year ago

Hi,

I can't seem to set a cookie with 150000 or more seconds.

I tested some values. 140000 seconds work. 150000 does not.

With 150000 seconds, the cookie get's deleted when the browser is closed.

This happens with the current version. Before I could store the cookie seven days without a problem.

Or am I just missing something (as usual).

Greetings
Frank


Replies (6)

RE: WApplication::setCookie() Bug? - Added by Koen Deforche over 1 year ago

Hey,

Do you see this problem with version 3.2.0 or current git, and with what browser ? I couldn't reproduce with the latter and Chrome.

Regards,
koen

RE: WApplication::setCookie() Bug? - Added by Frank B over 1 year ago

Hi Koen,

I'm using the official release 3.2.0.

I tried chrome and firefox.

Bye
Frank

RE: WApplication::setCookie() Bug? - Added by Frank B over 1 year ago

Oh, and I forgot to mention, I'm on windows.

Don't know if that has any relevance.

RE: WApplication::setCookie() Bug? - Added by Koen Deforche over 1 year ago

Hey,

Still no lucking reproducing with Wt 3.2.0.

Could you see what headers are being set in response to set-cookie ?
With Chrome you can do that using the web inspector and look for a request header 'Set-Cookie'.

Regards,
koen

RE: WApplication::setCookie() Bug? - Added by Frank B over 1 year ago

Hi Koen,

I can't find any headers regarding the cookie.

I can find it under the "Resources" Tab in Web Inspector (Expires = Session)

Stange... Yesterday it worked with 140000 seconds. Today it does not. Today it does work with 100000 seconds though...

I'm on another computer today, so maybe it's nothing, but... Today is the 29. Feb. Could it be related to the leapyear?

Bye
Frank

RE: WApplication::setCookie() Bug? - Added by Koen Deforche over 1 year ago

Hey,

I would be surprised if it was circumstancial to Feb 29 ... any more clues on how I can reproduce this, perhaps a working example ?

Regards,
koen

(1-6/6)