You do realise that Apache is a multi process web server. If the way
you have set session database is such that it is in memory things will
not work. This is because each process handling requests will be
referring to a different session database. When using Apache in multi
process configuration something like a session database has to be in a
shared resource accessible to all processes.
Graham
On Aug 28, 2:01 am, Petko <[EMAIL PROTECTED]> wrote:
> Hi everybody!
>
> To start, I am quite new to this group and to web.py in general. I
> will be very thankful if somebody from the community can help me with
> the problem that I have.
>
> Basically, I am writing a web application that uses version 0.23
> together with encrypted cookie-based beaker sessions (version 0.9.4).
> The web application performs an authentication step
> with a small login screen and saves the user info in the session
> cookie. Furthermore,
> all GET and POST methods in my controller classes are decorated with a
> decorator that
> looks in the session to check if the user is logged in. If not, then
> it redirects to the login page.
> Otherwise, it proceeds with the request. As far as I know, this is a
> standard way for doing access control in web.py. So far, so good.
>
> When I tested the application with the web.py's own web server
> (CherryPy/3.0.1), everything
> worked just fine. Then, I deployed it on Apache/2.2.8 (Ubuntu) with
> mod_wsgi and without
> any mod_rewrite rules and I encountered a very weird problem. After I
> log in, the application sets
> correctly the cookie in the browser that stores the user information,
> but on any subsequent
> XmlHttpRequest's (GET or POST) and sometimes when I reload the main
> page the beaker
> module does not like the cookie that is sent back to the web server.
> It just creates
> a new empty session, when I invoke session =
> web.ctx.environ['beaker.session'] in my code (which
> is essentially equal to a logout) and redirects me to the login
> screen.
>
> Here is a dump of the HTTP header of a request that is sent to the
> server, where the problem occurs (the dump was made in the web.py
> application by printing out web.ctx.environ):
>
> ctx.environ: {'mod_wsgi.reload_mechanism': '0',
> 'mod_wsgi.listener_port': '80', 'HTTP_REFERER': 'http://test/
> application.py/login', 'mod_wsgi.listener_host': '',
> 'beaker.get_session': <bound method SessionMiddleware._get_session of
> <beaker.middleware.SessionMiddleware object at 0x12eb690>>,
> 'SERVER_SOFTWARE': 'Apache/2.2.8 (Ubuntu) mod_python/3.3.1 Python/
> 2.5.2 mod_wsgi/1.3', 'SCRIPT_NAME': '/application.py',
> 'SERVER_SIGNATURE': '<address>Apache/2.2.8 (Ubuntu) mod_python/3.3.1
> Python/2.5.2 mod_wsgi/1.3 Server at test Port 80</address>\n',
> 'REQUEST_METHOD': 'GET', 'HTTP_KEEP_ALIVE': '300', 'SERVER_PROTOCOL':
> 'HTTP/1.1', 'QUERY_STRING': 'type=topic&id=all&_=1219850978947',
> 'PATH': '/usr/local/bin:/usr/bin:/bin', 'HTTP_ACCEPT_CHARSET':
> 'ISO-8859-1,utf-8;q=0.7,*;q=0.7', 'HTTP_USER_AGENT': 'Mozilla/5.0
> (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208
> Firefox/3.0.1', 'HTTP_CONNECTION': 'keep-alive', 'HTTP_COOKIE':
> 'sid=2d7e109489665220b0342dd4fc7881ee40d277eaaa5c64af17f6cd7e018d216202a756
> 46',
> 'SERVER_NAME': 'test', 'REMOTE_ADDR': '87.121.16.27',
> 'wsgi.url_scheme': 'http', 'mod_wsgi.output_buffering': '0',
> 'PATH_TRANSLATED': '/home/app/trunk/FeedFront/get_content',
> 'SERVER_PORT': '80', 'wsgi.multiprocess': True, 'SERVER_ADDR':
> '209.20.83.113', 'DOCUMENT_ROOT': '/home/app/trunk/FeedFront',
> 'mod_wsgi.process_group': '', 'HTTP_X_REQUESTED_WITH':
> 'XMLHttpRequest', 'SCRIPT_FILENAME': '/home/app/trunk/FeedFront/
> application.py', 'SERVER_ADMIN': '[EMAIL PROTECTED]', 'wsgi.input':
> <mod_wsgi.Input object at 0x1f8e7b0>, 'HTTP_HOST': 'test',
> 'beaker.session': {'_accessed_time': 1219851139.6110289,
> '_creation_time': 1219850922.7892039}, 'wsgi.multithread': False,
> 'mod_wsgi.callable_object': 'application', 'REQUEST_URI': '/
> application.py/get_content?type=topic&id=all&_=1219850978947',
> 'HTTP_ACCEPT': '*/*', 'wsgi.version': (1, 0), 'GATEWAY_INTERFACE':
> 'CGI/1.1', 'mod_wsgi.case_sensitivity': '1', 'wsgi.errors':
> <mod_wsgi.Log object at 0x1fcd150>, 'REMOTE_PORT': '4683',
> 'HTTP_ACCEPT_LANGUAGE': 'en-us,en;q=0.5', 'wsgi.run_once': False,
> 'mod_wsgi.application_group': 'test|/application.py',
> 'mod_wsgi.script_reloading': '1', 'HTTP_ACCEPT_ENCODING':
> 'gzip,deflate', 'PATH_INFO': '/get_content'}
>
> The cookie is sent obviously since 'HTTP_COOKIE':
> 'sid=2d7e109489665220b0342dd4fc7881ee40d277eaaa5c64af17f6cd7e018d216202a756
> 46'
>
> but here is what the beaker session contains:
> _accessed_time=1219851139.61, _creation_time=1219850922.79
>
> and here is what it should contain:
> loggedin=True, _accessed_time=1219851139.61,
> user=<app.models.User.User instance at 0x1549830>, _cr
> eation_time=1219850888.67
>
> I feel very confused with this problem and I don't know what
> additional information to provide, so please
> ask.
> Many thanks in advance!
>
> Petko
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web.py" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/webpy?hl=en
-~----------~----~----~----~------~----~------~--~---
