I can reproduce your behavior. The problem is that when you set response.cookies['LAST_FUNCTION'] = request.function
you are not setting a path response.cookies['LAST_FUNCTION']['path']='/myapplication' therefore the browser assumes the scope of the cookie is the URL. web2py cannot set the path (scope) automatically because it does not know how your application is exposed. For example: response.cookies['LAST_FUNCTION']['path']='/'+request.application would behave differently depending on the routes. I would not be tremendously opposed to changing this default but I am not convinced there is a better default. On Wednesday, 8 August 2012 18:25:36 UTC-5, Yarin wrote: > > This is a weird issue turned weirder, but I've at least been able to > reproduce it: > > *Controller:* > > def func_a(): > > response.cookies['LAST_FUNCTION'] = request.function > return str(request.cookies) > > def func_b(): > > response.cookies['LAST_FUNCTION'] = request.function > return str(request.cookies) > > > def dump_cookies(): > > return str(request.cookies) > > > > Make 5 calls in succession: > /func_a > /func_b (LAST_FUNCTION = 'func_a') > /func_a (LAST_FUNCTION = 'func_b') > /func_b (LAST_FUNCTION = 'func_a') > /dump_cookies (LAST_FUNCTION = 'func_b') > > Everything checks out. > > Now clear cookies, and try the calls again, but this time with different > args for each: > /func_a/1 > /func_b/2 > /func_a/1 (LAST_FUNCTION = 'func_a') > /func_b/2 (LAST_FUNCTION = 'func_b') > /dump_cookies -No LAST_FUNCTION cookie- > > In other words, the cookies are no longer being shared across functions! > > Please try this yourself and report back. If anyone can make sense of > this, I want to hear it... > > --
