Hi again,
i use sfPostgreSQLSessionStorage in a web server cluster and have no
problems.
For debugging your problem, i would write s small filter for that,
that logs session id and user id for every request. So you could
track down, when your session gets really lost.
Have you checked, if
One theory I had was that perhaps the slight discrepancies in system
time between servers is causing the sessions to become invalidated
(i.e. login on one server, session is created then view page on
another server and its 1 minute ahead/behind so session gets
invalidated).
I dont know enough abo
On Aug 20, 5:48 pm, Greg Freeman <[EMAIL PROTECTED]> wrote:
> Symfony uses session_name(). The name of the session is in your
> applications' factories.yml. It defaults to 'symfony'.
>
> That may be causing the problem.
No, we changed that to the name of the site.
--~--~-~--~~---
On Aug 20, 4:32 pm, Frank Stelzer <[EMAIL PROTECTED]> wrote:
> how do you manage your sessions? Are you using the standard
> serverside sessions or do you save your sessions in the database?
> Or to speak symfony: Do you use the sfSessionStorage or the
> sfMySQLSessionStorage as storage? I hop
Symfony uses session_name(). The name of the session is in your
applications' factories.yml. It defaults to 'symfony'.
That may be causing the problem.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"symfony users
Hi,
how do you manage your sessions? Are you using the standard
serverside sessions or do you save your sessions in the database?
Or to speak symfony: Do you use the sfSessionStorage or the
sfMySQLSessionStorage as storage? I hope you use the last one,
because is the only solution, where
