#10188: HttpResponse does not filter CR/LF characters from headers
-------------------------------------+-------------------------------------
Reporter: Bob Thomas | Owner:
| rokclimb15
Type: | Status: closed
Component: HTTP handling | Version: 1.0
Severity: | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* ui_ux: => 0
* easy: => 0
Comment:
In [changeset:"9bde906fb2b8f63f056284347c660a3fec92ef34" 9bde906]:
{{{
#!CommitTicketReference repository=""
revision="9bde906fb2b8f63f056284347c660a3fec92ef34"
Refs #10188 -- Added tests for BadHeaderErrors when HTTP header with
newlines cannot be encoded/decoded.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/10188#comment:14>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107017f59d545cc-991249ca-508e-4caf-ba5d-333529240795-000000%40eu-central-1.amazonses.com.
