On Thursday, October 22, 2009 3:34:03 AM UTC-4, SergeyPo wrote: > Yes I was running two different applications, and that's what wondered > me - why different apps (actually two different python web2py > processes) affected each other.
The issue may be the (internal) application name you are using. Web2py constructs the session ID cookie name as: response.session_id_name = 'session_id_%s' % masterapp.lower() where by default the masterapp = request.application. So you could have two different apps in the sense that they do different things and are known to users by different names; but if the web2py internal app name (name of the directory under web2py/applications where your app files live) has the same name, then the two apps would have conflicting session cookie names. e.g. if both apps were names app1 or default, this would happen. I believe this is only possible if you run the apps using separate web2py instances (like /path/to/web2py and /other/instance/of/web2py) on the same host; or on two hosts with routing rules that roll up both hosts under the same web virtual host / domain; since the directory under web2py/applications would have to be the same for the two apps but have different content. I.e. this seems like a bigger mystery if you were running the two apps / two ports from a single instance of web2py -- ??. --
