[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

lynx-dev multipart/form-data boundary

From: all kui
Subject: lynx-dev multipart/form-data boundary
Date: Fri, 1 Nov 2002 12:06:53 -0800 (PST)

in RFC 2388: Returning Values from Forms: 

in paragraph 4.1 "Boundary"
it says:
"As with other multipart types, a boundary is selected
that does not occur in any of the data."

later on it says:
..."For example"...

Now when I tested my code, that grabs data sent from a
multipart/form-data encoded form, I saw that Lynx
(versions 8.2.3 and 8.2.4 which I used) always
as a boundary.
In this boundary "xnyL" is the mirrored equivalent of
"Lynx" and "AaB03x" is being taken literally from the
author's example, but now with capital X at the end...

Other browsers use a "unique key" in their boundary
with the extra "--" at the start it would make:
that changes with every post of the form:
in Internet Explorer, or:
in Mozilla 1.0

To replicate the error that I came about do the
- Use a Lynx browser.
- Fill out a form with enctype="multipart/form-data"
- put "--xnyLAaB03X" in an input text field or
This will rise an error in the server code that has to
interpret the data.
To give an example: it wouldn't be possible to post
this very text in a multi-part/formdata encoded form
using Lynx!

I would propose using an equivalent approach (a unique
key) as used in other browsers and as:
RFC 1867 : Form-based File Upload in HTML
already proposed:
"A boundary is selected that does not occur in any of
the data. (This selection is sometimes done



Do you Yahoo!?
HotJobs - Search new jobs daily now

; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]