#28430: Response is not necessarrily rendered when response middlewares are
applied
--------------------------------------------+------------------------
Reporter: Sébastien Diemer | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
--------------------------------------------+------------------------
According to
[https://github.com/django/django/blob/master/django/core/handlers/base.py#L90
this part of the code], a request is not necessarily rendered when
response middlewares are applied.
However
[https://github.com/django/django/blob/master/django/middleware/common.py#L137
this part of the code] of CommonMiddleware assumes that the response is
already rendered (taking its content-length).
There seems to be an inconsistency here.
--
Ticket URL: <https://code.djangoproject.com/ticket/28430>
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/050.1764aba90fa2bc297526af779d7f8f91%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
