#27346: Stop setting the Content-Length header in ConditionalGetMiddleware
-------------------------------------+-------------------------------------
Reporter: Kevin Christopher | Owner: nobody
Henry |
Type: | Status: new
Cleanup/optimization |
Component: HTTP handling | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* needs_better_patch: => 0
* stage: Unreviewed => Accepted
* type: Uncategorized => Cleanup/optimization
* needs_tests: => 0
* needs_docs: => 0
Comment:
It was [https://github.com/django/django/pull/6798#issuecomment-227557147
discussed briefly] when adding `Content-Length` to `CommonMiddleware`. We
didn't see much advantage to removing it at the time as
`ConditionalGetMiddleware` might be used without `CommonMiddleware`. I
don't have a strong feeling about it though.
--
Ticket URL: <https://code.djangoproject.com/ticket/27346#comment:1>
Django <https://code.djangoproject.com/>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.3367882a77a8c1f32a019ae590aa25c3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
