|
/
Zope
/
Apsis
/
Pound Mailing List
/
Archive
/
2011
/
2011-04
/
sessions through out all servers
[
pound-2.6c multiple SSL certificates, comparing ... ]
[
ANNOUNCE: Pound - reverse proxy and load balancer ... ]
sessions through out all servers
Adrian Padilla <adrianp918(at)compumedik.com> |
2011-04-08 20:11:13 |
[ FULL ]
|
Hello everyone,
i have pound installed on ubuntu, 10.10
i ran into a problem with my setup, where i have webmail clients who try to
access the webmail app, and i have been getting complaints that they log in and
they get error saying not logged in. so i investigated this and i think i have
narrowed it down to a problem with sessions,
when they go tot he website
http://webmail.domain.com internally
it may be handed to one server but by time they log in it is being sent to
another server thus the error. is there a way to have all the session or
session information follow along with the login information or how would this
work,
the webmail application only uses php files, no database backend,
any information would be helpful
Adrian Padilla
|
|
|
RE: [Pound Mailing List] sessions through out all servers
"Jacob Anderson" <jwa(at)beyond-ordinary.com> |
2011-04-08 20:22:37 |
[ FULL ]
|
Adrian,
You need to have a common session server for your application. Pound does
not keep your session data, it only stores information about your session
that allows it to stick a user on a certain BE.
You need a common database. If you can't do this, then you will have
problems running a reverse proxied mail system like yours. Maybe there is a
PHP common session extension that allows you to replicate session across PHP
instances using something like Zend.
[...]
|
|
|
Re: [Pound Mailing List] sessions through out all servers
Emilio Campos <emilio.campos.martin(at)gmail.com> |
2011-04-08 20:55:07 |
[ FULL ]
|
You have to read how your webmail works with sessions, normally a php cookie
with session id is created , it is can be used with pound with session TYPE
directive.
example on google:
ListenHTTP
Address 127.0.0.1
Port 8000
xHTTP 2
End
Service
BackEnd
Address 127.0.0.1
Port 8080
End
BackEnd
Address 127.0.0.1
Port 8081
End
Session
Type COOKIE
ID "squirrelcookie"
TTL 300
End
End
ID is the name of cookie, created and saved on the client browser.
Regards!
2011/4/8 Jacob Anderson <jwa(at)beyond-ordinary.com>
[...]
[...]
|
|
|
|
|
|