Re: [Django] #19200: cached_db backend doesn't honor expiry time

2012-10-28 Thread Django
#19200: cached_db backend doesn't honor expiry time
--+--
 Reporter:  aaugustin |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.sessions  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by Aymeric Augustin ):

 In [changeset:"e6b0ee768c46368a41a5b278180d1d1ecbd3d5c6"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e6b0ee768c46368a41a5b278180d1d1ecbd3d5c6"
 [1.5.x] Improved tests introduced in 04b00b6.

 These tests are expected to fail for the file session backend because it
 doesn't handle expiry properly. They didn't because of an error in the
 test setup sequence.

 Refs #19200, #18194.

 Backport of 882c47c from master.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Django] #19200: cached_db backend doesn't honor expiry time

2012-10-28 Thread Django
#19200: cached_db backend doesn't honor expiry time
--+--
 Reporter:  aaugustin |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.sessions  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by Aymeric Augustin ):

 In [changeset:"882c47cd405cfd29194f2e968678a5aa1d6ec75f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="882c47cd405cfd29194f2e968678a5aa1d6ec75f"
 Improved tests introduced in 04b00b6.

 These tests are expected to fail for the file session backend because it
 doesn't handle expiry properly. They didn't because of an error in the
 test setup sequence.

 Refs #19200, #18194.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Django] #19200: cached_db backend doesn't honor expiry time

2012-10-27 Thread Django
#19200: cached_db backend doesn't honor expiry time
--+--
 Reporter:  aaugustin |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.sessions  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by Aymeric Augustin ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"0fe02feab43aa0f0d0608de85cff7183055e6dd7"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0fe02feab43aa0f0d0608de85cff7183055e6dd7"
 [1.5.x] Fixed #19200 -- Session expiry with cached_db

 Also did a little bit of cleanup.

 Backport of 04b00b6 from master.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Django] #19200: cached_db backend doesn't honor expiry time

2012-10-27 Thread Django
#19200: cached_db backend doesn't honor expiry time
--+--
 Reporter:  aaugustin |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.sessions  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by Aymeric Augustin ):

 In [changeset:"04b00b668d0d56c37460cbed19671f4b1b5916c3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="04b00b668d0d56c37460cbed19671f4b1b5916c3"
 Fixed #19200 -- Session expiry with cached_db

 Also did a little bit of cleanup.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [Django] #19200: cached_db backend doesn't honor expiry time (was: cached_db and signed_cookies backends don't honor expiry time)

2012-10-27 Thread Django
#19200: cached_db backend doesn't honor expiry time
--+--
 Reporter:  aaugustin |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.sessions  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by aaugustin):

 This will be easy to fix for cached_db, and very hard for signed_cookies.

 Signed cookies store the date of the signature, and the verification
 function takes a maximum age. Unfortunately, the maximum age is known when
 the cookie is signed, not when it's verified. Fixing this problem for
 signed cookies requires a redesign of the way session expiration is
 handled, which is covered by #19201.

 I'm updating the title to restrict this ticket to cached_db.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.