1.1 --- a/docs/parameters.html Tue Sep 06 22:03:41 2005 +0000
1.2 +++ b/docs/parameters.html Tue Sep 06 22:04:08 2005 +0000
1.3 @@ -1,19 +1,16 @@
1.4 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
1.5 -<html xmlns="http://www.w3.org/1999/xhtml">
1.6 -<head>
1.7 - <title>Request Parameters and Uploads</title>
1.8 - <meta name="generator"
1.9 - content="amaya 8.1a, see http://www.w3.org/Amaya/" />
1.10 - <link href="styles.css" rel="stylesheet" type="text/css" />
1.11 -</head>
1.12 +<html xmlns="http://www.w3.org/1999/xhtml"><head>
1.13 +
1.14 + <title>Request Parameters and Uploads</title><meta name="generator" content="amaya 8.1a, see http://www.w3.org/Amaya/" />
1.15 + <link href="styles.css" rel="stylesheet" type="text/css" /></head>
1.16 +
1.17 <body>
1.18 <h1>Request Parameters and Uploads</h1>
1.19 <p>Even though it is possible to expose different parts of an
1.20 application
1.21 using different <a href="paths.html">URLs and paths</a>, this usually
1.22 is only
1.23 -enough for applications which model some kind of <a
1.24 - href="paths-filesystem.html">filesystem</a> or repository.
1.25 +enough for applications which model some kind of <a href="paths-filesystem.html">filesystem</a> or repository.
1.26 Applications which
1.27 involve user input through forms, for example, need to be able to
1.28 receive
1.29 @@ -29,13 +26,11 @@
1.30 <li>The application reads the field values using the WebStack API.</li>
1.31 </ol>
1.32 <h2>Parameter Origins</h2>
1.33 -<p>Request parameters can originate from two sources:</p>
1.34 +<p>Request parameters exist in two forms:</p>
1.35 <ul>
1.36 - <li><a href="parameters-headers.html">Request headers</a> -
1.37 -parameters are found here when they are specified in the URL as a
1.38 + <li><a href="parameters-headers.html">Request header parameters</a> - parameters specified in the URL as a
1.39 "query string".</li>
1.40 - <li><a href="parameters-body.html">Request bodies</a> - parameters
1.41 -are found here when the POST <a href="methods.html">request method</a>
1.42 + <li><a href="parameters-body.html">Request body parameters</a> - parameters are found in the request body when the POST <a href="methods.html">request method</a>
1.43 is used.</li>
1.44 </ul>
1.45 <p>One useful application of parameters transferred in request bodies
1.46 @@ -57,9 +52,7 @@
1.47 <dd>This method returns a dictionary mapping field names to lists of
1.48 values for all known parameters. Each value will be a Unicode object.<br />
1.49 An optional <code>encoding</code> parameter may be used to assist the
1.50 -process of converting parameter values to Unicode objects - see <a
1.51 - href="parameters-body.html">"Request Body Parameters"</a> and <a
1.52 - href="encodings.html">"Character Encodings"</a> for more discussion of
1.53 +process of converting parameter values to Unicode objects - see <a href="parameters-body.html">"Request Body Parameters"</a> and <a href="encodings.html">"Character Encodings"</a> for more discussion of
1.54 this parameter.</dd>
1.55 <dt><code>get_query_string</code></dt>
1.56 <dd>This method returns the part of the URL which contains parameter
1.57 @@ -114,8 +107,6 @@
1.58 which describes the request body's contents.</dd>
1.59 </dl>
1.60 </div>
1.61 -<p>The purpose and behaviour of <code>PUT</code> <a
1.62 - href="methods.html">request methods</a> is described in the HTTP
1.63 +<p>The purpose and behaviour of <code>PUT</code> <a href="methods.html">request methods</a> is described in the HTTP
1.64 specification.</p>
1.65 -</body>
1.66 -</html>
1.67 +</body></html>
1.68 \ No newline at end of file