#24239: Possible problem in CVE-2015-0219 fix for 1.4.x
-------------------------------+------------------------------------
Reporter: rhertzog | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: 1.4
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
-------------------------------+------------------------------------
Comment (by carljm):
Actually, scratch that, the reason is clear. In July 2005, wsgiref was a
third-party library, it wasn't in the stdlib yet. So Adrian was just
copying code from it - at that time Django's `WSGIRequestHandler`
inherited from `BaseHTTPHandler`, which didn't have a `get_environ()`, of
course. So the custom `get_environ()` method never existed in order to
correct any issue in wsgiref - it was a straight-up copy and has been
superfluous ever since Django's `WSGIRequestHandler` began inheriting from
`wsgiref.simple_server.WSGIRequestHandler`.
--
Ticket URL: <https://code.djangoproject.com/ticket/24239#comment:4>
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/066.89cac5855e3d9c6577b7bd20ee06148a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
