tickets: 16182
This data as json
id | created | changetime | last_pulled_from_trac | stage | status | component | type | severity | version | resolution | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
16182 | 2011-06-09 10:53:19 | 2011-06-17 09:53:42 | 2022-03-06 04:02:30.021189 | Accepted | closed | Core (Other) | Bug | Normal | dev | wontfix | TimestampSigner should use a more precise timestamp | Generating a secure cookie using the TimestampSigner within the same second and the same data actually generates precisely the same cookie. I'm currently developing a cookie-based session backend, and this line keeps failing as a result, because cycling the cookie isn't really cycling the cookie: https://code.djangoproject.com/browser/django/trunk/django/contrib/sessions/tests.py#L153 I've attached a small patch that fixes the problem by increasing the precision. | floguy | floguy | 0 | 1 | 0 | 0 | 0 | 0 |