So it appears to be a bug... adding () after the decode on line 185 of redis_session.py appears to resolve the cause of this traceback.
However another issue has cropped up... every page hit results in a new session key being created which means they're unusable. Changing sessions from redis to the default disk based sessions works as expected so it appears to be something related to the redis implementation. Can anyone confirm whether they are using redis for sessions successfully in a configuration similar to the above? Thx, Jose -- 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 web2py+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/351997fc-76ca-4fbc-9290-61f2e84c4222%40googlegroups.com.
