An HTML form is a section of a document containing normal content, markup,
special elements called controls
(checkboxes, radio buttons, menus, etc.), and labels on those controls. Users
generally "complete" a form by modifying its controls (entering text, selecting
menu items, etc.), before submitting the form to an agent for processing (e.g.,
to a Web server, to a mail server, etc.)
Here's a simple form that includes labels, radio buttons, and push buttons
(reset the form or submit it):
A control's "control name" is given by its
name attribute. The scope of the name attribute for a
control within a FORM element is the FORM element.
Each control has both an initial value and a current value, both of which
are character strings. Please consult the definition of each control for
information about initial values and possible constraints on values imposed by
the control. In general, a control's "initial
value" may be specified with the control element's
value attribute. However, the initial value of a
TEXTAREA element is given by its contents, and the initial value of
an OBJECT element in a form is determined by the object
implementation (i.e., it lies outside the scope of this specification).
The control's "current value" is first set to the
initial value. Thereafter, the control's current value may be modified through
user interaction and scripts.
A control's initial value does not change. Thus, when
a form is reset, each control's current value is reset to its initial value. If
a control does not have an initial value, the effect of a form reset on that
control is undefined.
When a form is submitted for processing, some controls have their name
paired with their current value and these pairs are
submitted with the form. Those controls for which name/value pairs are
submitted are called successful
buttons: Push buttons have no default behavior. Each push button may
have client-side scripts associated with the
element's event attributes. When an event
occurs (e.g., the user presses the button, releases it, etc.), the associated
script is triggered.
Checkboxes (and radio buttons) are on/off switches that may be toggled by
the user. A switch is "on" when the control element's checked
attribute is set. When a form is submitted, only "on" checkbox controls can
Several checkboxes in a form may share the same
control name. Thus, for example, checkboxes allow users to select several
values for the same property. The INPUT element is used to create a
Radio buttons are like checkboxes except that when several share the same
control name, they are mutually exclusive: when one
is switched "on", all others with the same name are switched "off". The
INPUT element is used to create a radio button control.
If no radio button in a set sharing the same control name is initially
"on", user agent behavior for choosing which control is initially "on" is
undefined. Note. Since existing implementations handle this
case differently, the current specification differs from RFC 1866 ([RFC1866] section 188.8.131.52), which states:
At all times, exactly one of the radio buttons in a set is checked.
If none of the <INPUT> elements of a set of radio buttons specifies
`CHECKED', then the user agent must check the first radio button of the set
Since user agent behavior differs, authors should ensure that in each set of
radio buttons that one is initially "on".
Authors may create two types of controls that allow users to input text.
INPUT element creates a single-line input control and the
TEXTAREA element creates a multi-line input control. In both cases,
the input text becomes the control's current
Authors may create controls that are not rendered but whose values are
submitted with a form. Authors generally use this control type to store
information between client/server exchanges that would otherwise be lost due to
the stateless nature of HTTP (see [RFC2616]). The INPUT
element is used to create a hidden control.
Authors may insert generic objects in forms such that associated values are
submitted along with other controls. Authors create object controls with the
The elements used to create controls generally appear inside a FORM
element, but may also appear outside of a FORM element declaration when they are
used to build user interfaces. This is discussed in the section on intrinsic events. Note that controls outside a form
cannot be successful controls.
This attribute specifies which HTTP method will be used to submit the form data set. Possible (case-insensitive) values are
"get" (the default) and "post". See the section on
form submission for usage information.
This attribute specifies the list of character encodings for input
data that is accepted by the server processing this form. The value is a space-
and/or comma-delimited list of charset
values. The client must interpret this list as an exclusive-or list, i.e., the
server is able to accept any single character encoding per entity received.
The default value for this attribute is the reserved string "UNKNOWN". User
agents may interpret this value as the character encoding that was used to
transmit the document containing this FORM element.
This attribute specifies a comma-separated list of content types that a
server processing this form will handle correctly. User agents may use this
information to filter out non-conforming files when prompting a user to select
files to be sent to the server (cf. the INPUT element when
This attribute names the element so that it may be referred to from style
sheets or scripts. Note. This attribute has been included for
backwards compatibility. Applications should use the
id attribute to identify elements.
The layout of the form (given by the contents of the element).
The program that will handle the completed and submitted form (the action
attribute). The receiving program must be able to parse name/value pairs in
order to make use of them.
The method by which user data will be sent to the server (the method
A character encoding that must be accepted by the server in order to handle
this form (the accept-charset attribute). User agents may advise the
user of the value of the accept-charset attribute and/or
restrict the user's ability to enter unrecognized characters.
A form can contain text and markup (paragraphs, lists, etc.) in addition to
The following example shows a form that is to be processed by the "adduser"
program when submitted. The form will be sent to the program using the HTTP
<!ENTITY % InputType
"(TEXT | PASSWORD | CHECKBOX |
RADIO | SUBMIT | RESET |
FILE | HIDDEN | IMAGE | BUTTON)"
<!-- attribute name required for all but submit and reset -->
<!ELEMENT INPUT - O EMPTY -- form control -->
%attrs; -- %coreattrs, %i18n, %events --
type%InputType; TEXT -- what kind of widget is needed --
nameCDATA #IMPLIED -- submit as part of form --
valueCDATA #IMPLIED -- Specify for radio buttons and checkboxes --
checked (checked) #IMPLIED -- for radio buttons and check boxes --
disabled (disabled) #IMPLIED -- unavailable in this context --
readonly (readonly) #IMPLIED -- for text and passwd --
sizeCDATA #IMPLIED -- specific to each type of field --
maxlengthNUMBER #IMPLIED -- max chars for text fields --
src%URI; #IMPLIED -- for fields with images --
altCDATA #IMPLIED -- short description --
usemap%URI; #IMPLIED -- use client-side image map --
ismap (ismap) #IMPLIED -- use server-side image map --
tabindexNUMBER #IMPLIED -- position in tabbing order --
accesskey%Character; #IMPLIED -- accessibility key character --
onfocus%Script; #IMPLIED -- the element got the focus --
onblur%Script; #IMPLIED -- the element lost the focus --
onselect%Script; #IMPLIED -- some text was selected --
onchange%Script; #IMPLIED -- the element value was changed --
accept%ContentTypes; #IMPLIED -- list of MIME types for file upload --
Start tag: required, End tag:
This attribute specifies the type of
control to create. The default value for this attribute is "text".
This attribute tells the user agent the initial width of the control. The
width is given in pixels except when
type attribute has the value "text" or "password". In that case, its
value refers to the (integer) number of characters.
When the type attribute has the value "text" or "password",
this attribute specifies the maximum number of characters the user may enter.
This number may exceed the specified size, in which case the
user agent should offer a scrolling mechanism. The default value for this
attribute is an unlimited number.
Like "text", but the input text is
rendered in such a way as to hide the characters (e.g., a series of asterisks).
This control type is often used for sensitive input such as passwords. Note
that the current value is the text
entered by the user, not the text rendered by the user agent.
Note. Application designers should
note that this mechanism affords only light security protection. Although the
password is masked by user agents from casual observers, it is transmitted to
the server in clear text, and may be read by anyone with low-level access to
Creates a graphical submit button. The value
src attribute specifies the URI of the image that will decorate the
button. For accessibility reasons, authors should provide alternate text for the image via
the alt attribute.
When a pointing device is used to click on the
image, the form is submitted and the click coordinates passed to the
server. The x value is measured in
pixels from the left of the image, and the y value in pixels from the top of the image. The submitted
data includes name.x=x-value and
name.y=y-value where "name" is the value of the name attribute, and x-value and y-value
are the x and y coordinate values, respectively.
If the server takes different actions depending on the location clicked,
users of non-graphical browsers will be disadvantaged. For this reason, authors
should consider alternate approaches:
Use multiple submit buttons (each with its own image) in place of a single
graphical submit button. Authors may use style sheets to control the
positioning of these buttons.
Creates a file select control. User agents may
use the value of the value attribute as the initial file name.
17.4.2 Examples of forms containing INPUT
The following sample HTML fragment defines a simple form that allows the
user to enter a first name, last name, email address, and gender. When the
submit button is activated, the form will be sent to the program specified by
Please consult the section on intrinsic
events for more information about scripting and events.
The following example shows how the contents of a user-specified file may be
submitted with a form. The user is prompted for his or her name and a list of
file names whose contents should be submitted with the form. By specifying the
enctype value of "multipart/form-data", each file's contents will be
packaged for submission in a separate section of a multipart document.
What is your name? <INPUT type="text" name="name_of_sender">
What files are you sending? <INPUT type="file" name="name_of_files">
Buttons created with the BUTTON element function just like buttons
created with the INPUT element, but they offer richer rendering
possibilities: the BUTTON element may have content. For example, a BUTTON
element that contains an image functions like and may resemble an INPUT
element whose type is set to "image", but the BUTTON
element type allows content.
Visual user agents may render BUTTON buttons with relief and an
up/down motion when clicked, while they may render INPUT
buttons as "flat" images.
The following example expands a previous example, but creates submit and reset buttons with
BUTTON instead of INPUT. The buttons contain images by way of the
SELECT element is presented as a scrolled list box, this attribute
specifies the number of rows in the list that should be visible at the same
time. Visual user agents are not required to present a SELECT
element as a list box; they may use any other mechanism, such as a drop-down
SELECT element creates a menu. Each choice
offered by the menu is represented by an OPTION element. A SELECT
element must contain at least one OPTION element.
The OPTGROUP element allows authors to group choices
logically. This is particularly helpful when the user must choose from a long
list of options; groups of related choices are easier to grasp and remember
than a single long list of options. In HTML 4, all
OPTGROUP elements must be specified directly within a SELECT
element (i.e., groups may not be nested).
Zero or more choices may be pre-selected for the user. User agents should
determine which choices are pre-selected as follows:
OPTION element has the selected attribute set, user agent
behavior for choosing which option is initially selected is undefined.
Note. Since existing implementations handle this case differently, the
current specification differs from RFC 1866 ([RFC1866] section 8.1.3),
The initial state has the first option selected, unless a SELECTED
attribute is present on any of the <OPTION> elements.
Since user agent behavior differs, authors should ensure that each menu
includes a default pre-selected OPTION.
OPTION element has the selected attribute set, it should be
SELECT element has the multiple attribute set and more than
OPTION element has the selected attribute set, they should all
It is considered an error if more than one OPTION element has the
selected attribute set and the SELECT element does not have the
multiple attribute set. User agents may vary in how they handle this
error, but should not pre-select more than one choice.
Note. Implementors are advised that future versions of
HTML may extend the grouping mechanism to allow for nested groups (i.e.,
OPTGROUP elements may nest). This will allow authors to represent a
richer hierarchy of choices.
This attribute allows authors to specify a shorter label for an option than
the content of the OPTION element. When specified, user agents should use the
value of this attribute rather than the content of the OPTION
element as the option label.
The label attribute of the
OPTGROUP element specifies the label for a group of choices.
In this example, we create a menu that allows the user to select which of
seven software components to install. The first and second components are
pre-selected but may be deselected by the user. The remaining components are
not pre-selected. The size attribute states that the menu
should only have 4 rows even though the user may select from among 7 options.
The other options should be made available through a scrolling mechanism.
SELECT is followed by submit and reset buttons.
Only selected options will be successful
(using the control name "component-select"). When
no options are selected, the control is not successful and neither the name nor
any values are submitted to the server when the form is submitted. Note that
where the value attribute is set, it determines the control's
initial value, otherwise it's the element's
In this example we use the OPTGROUP element to group choices. The
<FORM action="http://somesite.com/prog/someprog" method="post">
<OPTION selected label="none" value="none">None</OPTION>
<OPTGROUP label="PortMaster 3">
<OPTION label="3.7.1" value="pm3_3.7.1">PortMaster 3 with ComOS 3.7.1</OPTION>
<OPTION label="3.7" value="pm3_3.7">PortMaster 3 with ComOS 3.7</OPTION>
<OPTION label="3.5" value="pm3_3.5">PortMaster 3 with ComOS 3.5</OPTION>
<OPTGROUP label="PortMaster 2">
<OPTION label="3.7" value="pm2_3.7">PortMaster 2 with ComOS 3.7</OPTION>
<OPTION label="3.5" value="pm2_3.5">PortMaster 2 with ComOS 3.5</OPTION>
<OPTION label="3.7R" value="IRX_3.7R">IRX with ComOS 3.7R</OPTION>
<OPTION label="3.5R" value="IRX_3.5R">IRX with ComOS 3.5R</OPTION>
Visual user agents may allow users to select
from option groups through a hierarchical menu or some other mechanism that
reflects the structure of choices.
A graphical user agent might render this as:
This image shows a SELECT element rendered as cascading menus. The top
label of the menu displays the currently selected value (PortMaster 3, 3.7.1).
The user has unfurled two cascading menus, but has not yet selected the new
value (PortMaster 2, 3.7). Note that each cascading menu displays the label of
OPTGROUP or OPTION element.
This attribute specifies the number of visible text lines. Users should be
able to enter more lines than this, so user agents should provide some means to
scroll through the contents of the control when the contents extend beyond the
This attribute specifies the visible width in average character widths.
Users should be able to enter longer lines than this, so user agents should
provide some means to scroll through the contents of the control when the
contents extend beyond the visible area. User agents may wrap visible text
lines to keep long lines visible without the need for scrolling.
This example creates a TEXTAREA control that is 20 rows by 80 columns
and contains two lines of text initially. The
TEXTAREA is followed by submit and reset buttons.
<FORM action="http://somesite.com/prog/text-read" method="post">
<TEXTAREA name="thetext" rows="20" cols="80">
First line of initial text.
Second line of initial text.
<INPUT type="submit" value="Send"><INPUT type="reset">
Setting the readonly attribute allows authors to display unmodifiable
text in a TEXTAREA. This differs from using standard marked-up text in
a document because the value of TEXTAREA is submitted with the
<FORM action="..." method="post">
<P>Enter your search phrase: <INPUT type="text"></P>
Semantics of ISINDEX.
Currently, the semantics for ISINDEX are only well-defined when the base URI
for the enclosing document is an HTTP URI. In practice, the input string is
restricted to Latin-1 as there is no mechanism for the URI to specify a
different character set.
This attribute explicitly associates the label being defined with another
control. When present, the value of this attribute must be the same as the
value of the id attribute of some other control in the same
document. When absent, the label being defined is associated with the element's
LABEL element may be used to attach information to controls. Each
LABEL element is associated with exactly one form control.
The for attribute associates a label with another control
explicitly: the value of the for attribute must be the same as the value of the
id attribute of the associated control element. More than one
LABEL may be associated with the same control by creating multiple
references via the for attribute.
This example creates a table that is used to align two text input controls and their associated labels. Each label
is associated explicitly with one text input:
To associate a label with another control
implicitly, the control element must be within the contents of the LABEL
element. In this case, the LABEL may only contain one control element. The label
itself may be positioned before or after the associated control.
In this example, we implicitly associate two labels with two text input controls:
<FORM action="..." method="post">
<INPUT type="text" name="firstname">
<INPUT type="text" name="lastname">
Note that this technique cannot be used when a table is being used for
layout, with the label in one cell and its associated control in another
When a LABEL element receives focus, it passes the focus on to its associated control. See the
section below on access keys for examples.
Labels may be rendered by user agents in a number of ways (e.g., visually,
read by speech synthesizers, etc.)
The FIELDSET element allows authors to group thematically
related controls and labels. Grouping controls makes it easier for users to
understand their purpose while simultaneously facilitating tabbing navigation
for visual user agents and speech navigation for speech-oriented user agents.
The proper use of this element makes documents more accessible.
LEGEND element allows authors to assign a caption to a
FIELDSET. The legend improves accessibility when the
FIELDSET is rendered non-visually.
In this example, we create a form that one might fill out at the doctor's
office. It is divided into three sections: personal information, medical
history, and current medication. Each section contains controls for inputting
the appropriate information.
<FORM action="..." method="post">
Last Name: <INPUT name="personal_lastname" type="text" tabindex="1">
First Name: <INPUT name="personal_firstname" type="text" tabindex="2">
Address: <INPUT name="personal_address" type="text" tabindex="3">
...more personal information...
value="Smallpox" tabindex="20"> Smallpox
value="Mumps" tabindex="21"> Mumps
value="Dizziness" tabindex="22"> Dizziness
value="Sneezing" tabindex="23"> Sneezing
...more medical history...
Are you currently taking any medication?
If you are currently taking medication, please indicate
it in the space below:
Note that in this example, we might improve the visual presentation of the
form by aligning elements within each FIELDSET (with style sheets), adding
color and font information (with style sheets), adding scripting (say, to only
open the "current medication" text area if the user indicates he or she is
currently on medication), etc.
In an HTML document, an element must receive focus from the user
in order to become active and perform its tasks. For example, users must
activate a link specified by the A element in order to follow the
specified link. Similarly, users must give a TEXTAREA focus in order to enter
text into it.
There are several ways to give focus to an element:
Designate the element with a pointing device.
Navigate from one element to the next with the keyboard. The document's
author may define a tabbing order that specifies the order in which
elements will receive focus if the user navigates the document with the
keyboard (see tabbing navigation). Once
selected, an element may be activated by some other key sequence.
Select an element through an access key
(sometimes called "keyboard shortcut" or "keyboard accelerator").
This attribute specifies the position of the current element in the tabbing
order for the current document. This value must be a number between 0 and
32767. User agents should ignore leading zeros.
The tabbing order
defines the order in which elements will receive focus when navigated by the
user via the keyboard. The tabbing order may include elements nested within
Elements that may receive focus should be navigated by user agents according
to the following rules:
Those elements that support the tabindex attribute and assign a
positive value to it are navigated first. Navigation proceeds from the element
with the lowest tabindex value to the element with the highest value. Values
need not be sequential nor must they begin with any particular value. Elements
that have identical tabindex values should be navigated in the order they
appear in the character stream.
Those elements that do not support the tabindex attribute or support it
and assign it a value of "0" are navigated next. These elements are navigated
in the order they appear in the character stream.
Elements that are disabled do not participate in
the tabbing order.
In this example, the tabbing order will be the BUTTON,
INPUT elements in order (note that "field1" and the button share the
same tabindex, but "field1" appears later in the character stream), and finally
the link created by the A element.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
<TITLE>A document with FORM</TITLE>
<P>Go to the
<A tabindex="10" href="http://www.w3.org/">W3C Web site.</A>
<BUTTON type="button" name="get-database"
Get the current database.
<FORM action="..." method="post">
<INPUT tabindex="1" type="text" name="field1">
<INPUT tabindex="2" type="text" name="field2">
<INPUT tabindex="3" type="submit" name="submit">
Tabbing keys. The actual key sequence that causes
tabbing navigation or element activation depends on the configuration of the
user agent (e.g., the "tab" key is used for navigation and the "enter" key is
used to activate a selected element).
User agents may also define key sequences to navigate the tabbing order
in reverse. When the end (or beginning) of the tabbing order is reached, user
agents may circle back to the beginning (or end).
This attribute assigns an access key to an element. An access
key is a single character from the document character set.
Note. Authors should consider the input method of the expected reader
when specifying an accesskey.
Pressing an access key assigned to an element gives focus to the
element. The action that occurs when an element receives focus
depends on the element. For example, when a user activates a link defined by
A element, the user agent generally follows the link. When a user
activates a radio button, the user agent changes the value of the radio button.
When the user activates a text field, it allows input, etc.
This example assigns the access key "U" to a label associated with an
INPUT control. Typing the access key gives focus to the label which
in turn gives it to the associated control. The user may then enter text into
<FORM action="..." method="post">
<LABEL for="fuser" accesskey="U">
<INPUT type="text" name="user" id="fuser">
In this example, we assign an access key to a link defined by the A
element. Typing this access key takes the user to another document, in this
case, a table of contents.
Table of Contents</A>
The invocation of access keys depends on the underlying system. For
instance, on machines running MS Windows, one generally has to press the "alt"
key in addition to the access key. On Apple systems, one generally has to press
the "cmd" key in addition to the access key.
The rendering of access keys depends on the user agent. We recommend that
authors include the access key in label text or wherever the access key is to
apply. User agents should render the value of an access key in such a way as to
emphasize its role and to distinguish it from other characters (e.g., by
In contexts where user input is either undesirable or irrelevant, it is
important to be able to disable a control or render it read-only. For example,
one may want to disable a form's submit button until the user has entered some
required data. Similarly, an author may want to include a piece of read-only
text that must be submitted as a value along with the form. The following
sections describe disabled and read-only controls.
For radio buttons that share the same value of the
name attribute, only the "on" radio button may be successful.
For menus, the control name
is provided by a SELECT element and values are provided by OPTION
elements. Only selected options may be successful. When no options are
selected, the control is not successful and neither the name nor any values are
submitted to the server when the form is submitted.
The current value
of a file select is a list of one or more file
names. Upon submission of the form, the contents of each file are
submitted with the rest of the form data. The file contents are packaged
according to the form's content type.
The current value of an object control is determined by the object's
If a control doesn't have a current value when
the form is submitted, user agents are not required to treat it as a successful
Furthermore, user agents should not consider the following controls
Finally, the encoded data is sent to the processing agent designated by the
action attribute using the protocol specified by the method
This specification does not specify all valid submission methods or content types that may be used with forms. However,
HTML 4 user agents must support the established conventions in the following
method is "get" and the action is an HTTP URI, the user agent
takes the value of action, appends a `?' to it, then appends the
form data set, encoded using the
type. The user agent then traverses the link to this URI. In this scenario,
form data are restricted to ASCII codes.
method is "post" and the action is an HTTP URI, the user agent
conducts an HTTP "post" transaction using the value of the action
attribute and a message created according to the
content type specified by the enctype attribute.
For any other value of action or method, behavior is unspecified.
User agents should render the response from the HTTP "get" and "post"
enctype attribute of the FORM element specifies the content type used to encode the form data set for submission to the server. User agents
must support the content types listed below. Behavior for other content types
This is the default content type. Forms submitted with this content type
must be encoded as follows:
Control names and values are escaped. Space characters are replaced by
`+', and then reserved characters are escaped as described in
[RFC1738], section 2.2: Non-alphanumeric characters are replaced by
`%HH', a percent sign and two hexadecimal digits representing the ASCII
code of the character. Line breaks are represented as "CR LF" pairs (i.e.,
The control names/values are listed in the order they appear in the
document. The name is separated from the value by `=' and
name/value pairs are separated from each other by `&'.
Note. Please consult [RFC2388] for additional
information about file uploads, including backwards compatibility issues, the
relationship between "multipart/form-data" and other content types, performance
The content type "application/x-www-form-urlencoded" is inefficient for
sending large quantities of binary data or text containing non-ASCII
characters. The content type "multipart/form-data" should be used for
submitting forms that contain files, non-ASCII data, and binary data.
The content "multipart/form-data" follows the rules of all multipart MIME
data streams as outlined in [RFC2045]. The definition
of "multipart/form-data" is available at the [IANA] registry.
A "multipart/form-data" message contains a series of parts, each
representing a successful control. The parts
are sent to the processing agent in the same order the corresponding controls
appear in the document stream. Part boundaries should not occur in any of the
data; how this is done lies outside the scope of this specification.
As with all multipart MIME types, each part has an optional "Content-Type"
header that defaults to "text/plain". User agents should supply the
"Content-Type" header, accompanied by a "charset" parameter.
Each part is expected to contain:
a "Content-Disposition" header whose value is "form-data".
a name attribute specifying the control name of
the corresponding control. Control names originally encoded in non-ASCII character sets may be encoded using the method
outlined in [RFC2045].
Thus, for example, for a control named "mycontrol", the corresponding part
would be specified:
Content-Disposition: form-data; name="mycontrol"
As with all MIME transmissions, "CR LF" (i.e., `%0D%0A') is
used to separate lines of data.
Each part may be encoded and the "Content-Transfer-Encoding" header supplied
if the value of that part does not conform to the default (7BIT) encoding (see
[RFC2045], section 6)
If the contents of a file are submitted with a form, the file input should
be identified by the appropriate
content type (e.g., "application/octet-stream"). If multiple files are to
be returned as the result of a single form entry, they should be returned as
"multipart/mixed" embedded within the "multipart/form-data".
The user agent should attempt to supply a file name for each submitted file.
The file name may be specified with the "filename" parameter of the
'Content-Disposition: form-data' header, or, in the case of multiple files, in
a 'Content-Disposition: file' header of the subpart. If the file name of the
client's operating system is not in US-ASCII, the file name might be
approximated or encoded using the method of [RFC2045]. This is
convenient for those cases where, for example, the uploaded files might contain
references to each other (e.g., a TeX file and its ".sty" auxiliary style
The following example illustrates "multipart/form-data" encoding. Suppose we
have the following form:
What is your name? <INPUT type="text" name="submit-name"><BR>
What files are you sending? <INPUT type="file" name="files"><BR>
<INPUT type="submit" value="Send"> <INPUT type="reset">
If the user enters "Larry" in the text input, and selects the text file
"file1.txt", the user agent might send back the following data: