Re: [Django] #26447: Remove USE_ETAGS setting

[Django]

#26447: Remove USE_ETAGS setting
--+
 Reporter:  syphar|Owner:  syphar
 Type:  Cleanup/optimization  |   Status:  new
Component:  HTTP handling |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * component:  Uncategorized => HTTP handling


--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.5c7ae7b8376dc9643b72a6460dfef346%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26447: Remove USE_ETAGS setting

[Django]

#26447: Remove USE_ETAGS setting
--+
 Reporter:  syphar|Owner:  syphar
 Type:  Cleanup/optimization  |   Status:  new
Component:  Uncategorized |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 Left comments for improvement on the
 [https://github.com/django/django/pull/6393 PR].

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.3aade101e4d14d7634a28e3b985b2ea0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26447: Remove USE_ETAGS setting

[Django]

#26447: Remove USE_ETAGS setting
--+
 Reporter:  syphar|Owner:  syphar
 Type:  Cleanup/optimization  |   Status:  new
Component:  Uncategorized |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by syphar):

 * needs_better_patch:   => 0
 * has_patch:  0 => 1
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 (after some discussions here at the DjangoCon springs I've just set the
 triage state :) )

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.c9fb090084ad7b67539d8a837341c6d1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26447: Remove USE_ETAGS setting

[Django]

#26447: Remove USE_ETAGS setting
--+
 Reporter:  syphar|  Owner:  syphar
 Type:  Cleanup/optimization  | Status:  new
Component:  Uncategorized |Version:  1.9
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 (with deprecation)

 In my opinion this setting is not needed (any more)

 - Conditional-Get handling can happen in the ConditionalGetMiddleware, not
 in CommonMiddleware any more
 - using or not using the middleware is (nearly) the same as setting
 USE_ETAGS or not
 - ETag Calculation can happen also in the middleware

 this also will fix a problem when you use the GZipMiddleware in
 combination with the Conditional-Get handling in CommonMiddleware.



 Open questions for me:
 - ConditionalGetMiddleware also handles Last-Modified/If-Modified-Since ,
 which CommonMiddleware didn't. I don't see a problem in throwing them
 together and activating/deactivating them together. You?

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/049.9b0eb398957fa13cae689d984147dedf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.