On Sep 25, 1:56 pm, Ian Lewis <[email protected]> wrote: > [...] unless accessing > COOKIES gives you raw values of ALL cookies and SIGNED_COOKIES > attempts to unsign ALL cookies. That seems really clunky.
Yes, all cookies would stay in COOKIES. SIGNED_COOKIES would be a lazy dict-like object, not a plain dictionary. It'd only unsign all cookies if you iterated its keys or values. But I just realised it doesn't cover the case for using a different signing key (or extra signing data though). I think I now prefer Simon's request.COOKIES.get_signed(key) method (which could handle different/extra signing data). I really don't like the term "unsigning" (and therefore don't like the method name unsign_cookie) - it doesn't explain what is happening clearly. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
