#12578: multipartparser.Parser does not accept non-canonical bare CR and bare LF
------------------------------------+---------------------------------------
Reporter: jfenwick | Owner: nobody
Status: closed | Milestone:
Component: HTTP handling | Version: 1.1
Resolution: invalid | Keywords: jython
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Comment (by kmtracey):
Ah, so it's not some client that is sending LF-only in the POST data,
since I gather the clients in use here are standard browsers, which will
be sending CRLFs. Interesting it only happens on Windows, where CRLF is
the "normal" line ending. It sounds like some code that is passing along
the post data is translating CRLFs to just LFs. Besides causing this
problem that behavior has the potential for corrupting binary files
uploaded to a Django server. All the code touching this data before
feeding it to the Django code needs to be treating it as binary, not text,
and not doing any type of line normalization.
--
Ticket URL: <http://code.djangoproject.com/ticket/12578#comment:7>
Django <http://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 post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
