ToasterChicken

The issue is because the session middleware is always handling every request as needing session data to persist, even if it was already present. If the scope has data the...

Using the session middleware with a JWS token provided by an external service was my intention with what I was considering it for. The method which the session is taking...

Too add, regarding the concern of getting the timestamp, it's in the cookie value string which is base64 encoded. The string has 3 parts, the Payload, Timestamp and Signature separated...

@Kludex I linked an issue and a discussion for the two changes submitted for this PR. When I say there's two changes, there's two changes including their associated test updates...

This PR #2501 appears to be for the responses module, the Sessions Middleware isn't currently using the responses module for cookie handling or http.cookies. It is somewhat unfortunate that there's...