#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):
Note even if Django is correct per the RFC, if there are non-compliant
clients in the wild that Django can't deal with because it is strictly
enforcing the RFC then we might want to look at relaxing the Django
implementation here. Particularly if there are other server side
implementations that these clients can work properly with. Adhering to
standards is great, but if it gets in the way of interoperating with real
clients that don't have issues with other servers then I don't know we'd
want to stick with a stance of "we're correct per the RFC". Hence the
request for more information. It'd be good to know what these clients are
(Barney's home-grown client used by exactly 8 machines on the internet or
something a little more popular?) and some information about servers that
they currently don't have trouble with.
--
Ticket URL: <http://code.djangoproject.com/ticket/12578#comment:5>
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.
