Hi Jacco
The stack is nginx -> apache with wsgi.
nginx caching is turned for some url patterns.
Thanks
On Fri, Jan 6, 2012 at 3:50 PM, Jacco Flenter wrote:
> What kind of software stack are you running? Apache and... or nginx and...?
>
>
> On Fri, Jan 6, 2012 at 10:51 AM, Arun P wrote:
>
>> @
What kind of software stack are you running? Apache and... or nginx and...?
On Fri, Jan 6, 2012 at 10:51 AM, Arun P wrote:
> @Kevin:
>
> The backend used is the default Database backend.
> There are no other projects which share the same domain space.
>
> I guess will have to write a middleware
@Kevin:
The backend used is the default Database backend.
There are no other projects which share the same domain space.
I guess will have to write a middleware to see what is happening to the
cookies.
Thanks.
On Fri, Jan 6, 2012 at 2:26 PM, Kevin wrote:
> Which backend is storing the session
Which backend is storing the session data? If session data is being
stored in the cache(which is normally the recommended way), what
caching backend are you using? If you are using locmem cache backend,
this might be your problem, change the cache backend to something more
stable for production.
On Thu, Jan 5, 2012 at 2:35 PM, Dennis Lee Bieber wrote:
> That would have to be a very erratic clock setting -- are there
> systems that don't use an NTP server to synchronize the clock? (I think
> all of my computers synchronize on a weekly basis).
virtual machines can have terribly erra
Could an incorrect computer clock contribute to this kind of issue?
On Thu, Jan 5, 2012 at 10:35 AM, Dennis Lee Bieber
wrote:
> On Thu, 5 Jan 2012 08:56:57 +0530, Arun P wrote:
>
>>That’s a lot of education Dennis. Thanks.
>
> Pardon, but just who were you replying to? Consider whose
> at
Also, as n FYI I don’t need to close the browser. It’s just refresh that
takes me to the login page.
Also the wifi login page does not come into play.
When I check the cookies all I can see is 2 related to Django sessionid &
csrf. And sessionid is just a unique long string
On Thu, Jan 5, 2012
That’s a lot of education Dennis. Thanks.
But, gmail is cookie login based and I don’t get logged out from Gmail.
If this is case why different behaviors?
On Wed, Jan 4, 2012 at 11:36 PM, Cherian Thomas wrote:
> Do you have the SESSION_COOKIE_NAME set correctly?
>
> Regards,
> Cherian
>
>
>
> On
Do you have the SESSION_COOKIE_NAME set correctly?
Regards,
Cherian
On Wed, Jan 4, 2012 at 9:21 PM, arun.pbk wrote:
>
> I have a Django app using Django social with session timeout set as
> SESSION_COOKIE_AGE = 60 * 60 *24 * 7
> The session is being store in the db and rows are inserted for n
I have a Django app using Django social with session timeout set as
SESSION_COOKIE_AGE = 60 * 60 *24 * 7
The session is being store in the db and rows are inserted for new
sessions with correct session id and expire dates.
Even though the session timeout is set to a week the users are
complaining
10 matches
Mail list logo
