Re: handling multipart/form-data uploads
- From: "Donal K. Fellows" <donal.k.fellows@xxxxxxxxxxxxxxxx>
- Date: Mon, 20 Sep 2010 01:41:53 -0700 (PDT)
On 20 Sep, 01:27, "tom.rmadilo" <tom.rmad...@xxxxxxxxx> wrote:
Of course the problem is not CRLF, but allowing CR, LF and CRLF to end
lines. For some odd reason email encoding works very well with
CRLF...because it disallows CR and LF within lines and the CRLF is not
part of the data. The reason for the encoding is obvious: email
messages last forever, so a simple "usually works" encoding can't work
with email.
For textual network protocols, you usually want to force the use of
crlf for end-of-line sequence; that's typically what the specification
of the protocol states. (Well, either that or binary of course.)
Donal.
.
- Follow-Ups:
- Re: handling multipart/form-data uploads
- From: tom.rmadilo
- Re: handling multipart/form-data uploads
- References:
- handling multipart/form-data uploads
- From: Tcl Bliss
- Re: handling multipart/form-data uploads
- From: Alexandre Ferrieux
- Re: handling multipart/form-data uploads
- From: tom.rmadilo
- handling multipart/form-data uploads
- Prev by Date: Re: from curl command to TclCurl
- Next by Date: Re: Network start-up in freewrap
- Previous by thread: Re: handling multipart/form-data uploads
- Next by thread: Re: handling multipart/form-data uploads
- Index(es):
Relevant Pages
|
