On Tuesday, December 23, 2014 4:56:15 PM UTC-5, Mike Orr wrote:
>
> Works. I'll just need to write a script to dump the session.
I like do to things like this in behind a /admin page, this way I can see
everything in real time (and use pprrint)
--
You received this message because you are s
OK.
redis_key = pyramid.session.signed_deserialize(COOKIE_VALUE, SECRET)
Works. I'll just need to write a script to dump the session.
On Tue, Dec 23, 2014 at 1:30 PM, Jonathan Vanasco wrote:
> Yeah, it's because the cookievalue is signed:
>
>
> https://github.com/ericrasmussen/pyramid_redis_ses
Yeah, it's because the cookievalue is signed:
https://github.com/ericrasmussen/pyramid_redis_sessions/blob/master/pyramid_redis_sessions/__init__.py
Using the pyramid functions by default, which serializes to b64:
https://github.com/Pylons/pyramid/blob/master/pyramid/session.py#L47-L10
I'm using pyramid_redis_sessions and want to check the session's data
in the session store. In Pylons I looked for the session ID in the
session cookie and it was the same ID in the session store. But in
Pyramid they're different, I guess because of cookie signing. So right
now my request header is
On Tue, Dec 23, 2014, 04:35 pyramidX wrote:
Extracting the appstruct logic into a separate function is one way to go,
though it still would be useful to have a way to conveniently create
peppercorn POST values from appstructs. Especially for cases where the view
logic is quite simple boilerplate
Extracting the appstruct logic into a separate function is one way to go,
though it still would be useful to have a way to conveniently create
peppercorn POST values from appstructs. Especially for cases where the view
logic is quite simple boilerplate (validate the form, submit the resulting
a
