Re: CRLF vs just LF in multipart parser
On Tue, Dec 15, 2009 at 7:33 PM, Dave Peck wrote: > Hello, > > I notice that Django's multipart form parser expects CRLF-style line > endings. Specifically, > django.http.multipartparser::parse_boudary_stream has a hardcoded > expectation of '\r\n\r\n' to end a part header. > > Is this line ending mandated by RFCs, or is this hardcoding a mistake? > > Reads like mandated to me: http://www.ietf.org/rfc/rfc2616.txt, section 3.7.2 (Multipart Types) http://www.ietf.org/rfc/rfc2046.txt Karen -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
CRLF vs just LF in multipart parser
Hello, I notice that Django's multipart form parser expects CRLF-style line endings. Specifically, django.http.multipartparser::parse_boudary_stream has a hardcoded expectation of '\r\n\r\n' to end a part header. Is this line ending mandated by RFCs, or is this hardcoding a mistake? I ask because I appear to have an external client that only sends LF- only endings; this causes Django to miss the entire contents of the form post. Thanks, Dave -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
