Re: gae-sessions

[David Underhill]

Hi Chris,

It turns out that Internet Explorer was deleting the gae-sessions when the browser was closed because it (apparently) only supports timestamps specified in GMT.  gae-sessions v1.02 and earlier, however, specified cookie timestamps in PST.  This caused IE to ignore the specified expiration time, and make the cookies only last until the browser was closed.

I've released gae-sessions v1.03 to fix this IE compatibility issue.  Thanks a ton for reporting the problem!

All the best,

~ David

On Thu, Jul 22, 2010 at 23:34, Chris Lacy <gday...@gmail.com> wrote:

Hi David,

Yes, the behaviour you've described below exactly matches our reproducable case for the bug.

It's strange. But as I'm sure you're aware, such is life with IE unfortunately :(

Many thanks for taking the time to look at this for us :)

Chris

On Fri, Jul 23, 2010 at 12:54 PM, David Underhill <d...@cs.stanford.edu> wrote:

Hi Chris,

I've been able to reproduce the problem using IE8 and the simple demo app included with gae-sessions.  IE8 works fine as long as I don't close the browser - I can navigate to another page and come back.  But when I close the browser and then start it again, it doesn't send the cookies to server anymore.  This is strange because it sends the cookies just fine for as long as I keep the browser open.

Anyway, it seems like IE8 is discarding the cookies once the browser is closed.  I don't see any cookie files saved on my computer.  I'm not sure why this is happening yet, but I'm going to figure it out ASAP.

All the best,

~ David

On Thu, Jul 22, 2010 at 10:44, Chris Lacy <gday...@gmail.com> wrote:

Hi David,

Thanks for getting back to me.

I've been using the logs constantly as a form of debugging what's going on. As best I can tell, there are no error messages (or logs in general) coming from gae-sessions.

Also, ATM there would likely be < 1KB of data being saved in total. When the session starts it's only 2 variables worth. Growing to maxium 3 variables. 

I plan on growing the usage of Sessions a lot once we can iron out the kinks here.

[...]

The main issue to note is that if you hit 'save' on IE, you character doesn't actually save next time you load the game in a new browser session (all other browsers work correctly). The reason being is that we're storing a Facebook access token in the session during application handshaking. But with IE, this token isn't retrieved due to the session not being able to be loaded.

Thanks again for your time :)

Chris

On Thu, Jul 22, 2010 at 9:56 PM, David Underhill <d...@cs.stanford.edu> wrote:

Chris,

Interesting; I'll definitely look into this afternoon and get back to you.  A few quick questions:

1) In the admin logs, do you see any error message(s) from gae-sessions?  I suspect there is probably something about a bad signature or such in the logs.

2) When you're starting the session, how much data are you storing in it?  (A few small values of total size about 1kB or less, etc.)

Sorry I'm just getting back to you now - somehow I overlooked your e-mail yesterday!

All the best,

~ David

On Wed, Jul 21, 2010 at 03:08, Chris Lacy <gday...@gmail.com> wrote:

Hi David,

I'm using your gae-sessions package in one of my applications.

First of all, thank you for making this project open source. It is much appreciated. I found it very easy to slot into our project, which was excellent.

However, I'm left with a very nasty issue in my code, where get_current_session() returns None under IE (tested in 7 & 8). Chrome, Safari and Firefox all return a valid session every time. Yet IE constantly returns None (100% of the time, on multiple machines). 

Have you ever come across any browser specific issues such as this with gae-sessions? Do you have any pointers as to what I might be doing wrong, or how I might go about fixing this issue?

Thanks in advance,

Chris Lacy

[jalsop]

David,

Very useful and well-written package!

Speaking of expiration, I notice that gae-sessions doesn't
automatically
extend the cooke expiry when a page is accessed.

I'd like to have a session that expires after say 30 minutes of
inactivity.

What's the best way to achieve this? Call regenerate_id() on every
page access?

Thanks,

- John Alsop

On Jul 24, 3:48 pm, David Underhill <d...@cs.stanford.edu> wrote:
> Hi Chris,
>

> It turns out that Internet Explorer was deleting the gae-sessions when the
> browser was closed because it (apparently) only supports timestamps
> specified in GMT.  gae-sessions v1.02 and earlier, however, specified cookie
> timestamps in PST.  This caused IE to ignore the specified expiration time,
> and make the cookies only last until the browser was closed.
>
> I've released gae-sessions v1.03 to fix this IE compatibility issue.  Thanks
> a ton for reporting the problem!
>
> All the best,
>
> ~ David
>

> On Thu, Jul 22, 2010 at 23:34, Chris Lacy <gdaych...@gmail.com> wrote:
> > Hi David,
>
> > Yes, the behaviour you've described below exactly matches our reproducable
> > case for the bug.
>
> > It's strange. But as I'm sure you're aware, such is life with IE
> > unfortunately :(
>
> > Many thanks for taking the time to look at this for us :)
>
> > Chris
>
> > On Fri, Jul 23, 2010 at 12:54 PM, David Underhill <d...@cs.stanford.edu>wrote:
>
> >> Hi Chris,
>
> >> I've been able to reproduce the problem using IE8 and the simple demo app
> >> included with gae-sessions.  IE8 works fine as long as I don't close the
> >> browser - I can navigate to another page and come back.  But when I close
> >> the browser and then start it again, it doesn't send the cookies to server
> >> anymore.  This is strange because it sends the cookies just fine for as long
> >> as I keep the browser open.
>
> >> Anyway, it seems like IE8 is discarding the cookies once the browser is
> >> closed.  I don't see any cookie files saved on my computer.  I'm not sure
> >> why this is happening yet, but I'm going to figure it out ASAP.
>
> >> All the best,
>
> >> ~ David
>