Please open a ticket about this.
On Thursday, 19 September 2013 13:07:38 UTC-5, Joel Rathgaber wrote: > > We are putting things in the session, so it shouldn't be empty. The line > in our code that is failing is something like this > > current.response.cookies[current.response.session_id_name]["httponly"] = > True > We are doing this in a module. > > In our models/db.py we have > session.connect(request, response, db=MEMDB(cache.memcache)) > (we set up memcache before this obviously). > > the error I'm getting is a KeyError in regards to the > current.response.cookies. Upon debugging, the current.response.cookies is > an empty SimpleCookie instance. > > I looked through the connect() method in the globals.py and could not see > any place that the cookies were assigned in the response object (as there > was in the 2.5 version of globals.py). > > Thanks! > --Joel. > > > > > On Thursday, September 19, 2013 10:39:56 AM UTC-6, Massimo Di Pierro wrote: >> >> If the session is empty it is not saved. If it is not saved there is no >> point in assigning a cookie. >> >> On Thursday, 19 September 2013 11:13:42 UTC-5, Joel Rathgaber wrote: >>> >>> Hey all, >>> >>> I've noticed that in the 2.5 and prior releases that the session id >>> cookie was sent back to the client in every response, and it seems like in >>> 2.6 it doesn't do this anymore. Is this by design? If so, what's the >>> reasoning? >>> >>> Thanks! >>> --Joel. >>> >>> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
