1.1 --- a/docs/parameters-body.html Tue Sep 06 22:03:41 2005 +0000
1.2 +++ b/docs/parameters-body.html Tue Sep 06 22:04:08 2005 +0000
1.3 @@ -1,24 +1,17 @@
1.4 -<?xml version="1.0" encoding="iso-8859-1"?>
1.5 -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
1.6 - "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
1.7 -<html xmlns="http://www.w3.org/1999/xhtml">
1.8 -<head>
1.9 - <title>Request Body Parameters</title>
1.10 - <meta name="generator" content="amaya 8.1a, see http://www.w3.org/Amaya/" />
1.11 - <link href="styles.css" rel="stylesheet" type="text/css" />
1.12 -</head>
1.13 +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
1.14 +<html xmlns="http://www.w3.org/1999/xhtml"><head>
1.15 +
1.16 + <title>Request Body Parameters</title><meta name="generator" content="amaya 8.1a, see http://www.w3.org/Amaya/" />
1.17 + <link href="styles.css" rel="stylesheet" type="text/css" /></head>
1.18 +
1.19
1.20 <body>
1.21 <h1>Request Body Parameters</h1>
1.22
1.23 <p>Request parameters are typically added to the request body when forms are
1.24 -submitted by a browser which is instructed to use the <code>POST</code> <a
1.25 -href="methods.html">request method</a>. A Web form (in HTML) can be used to
1.26 +submitted by a browser which is instructed to use the <code>POST</code> <a href="methods.html">request method</a>. A Web form (in HTML) can be used to
1.27 achieve this; for example:</p>
1.28 -<pre><form method="POST" action="http://www.boddie.org.uk/application">
1.29 - <input name="param1" type="text" />
1.30 - <input name="param2" type="text" />
1.31 -</form></pre>
1.32 +<pre><form method="POST" action="http://www.boddie.org.uk/application"><br /> <input name="param1" type="text" /><br /> <input name="param2" type="text" /><br /></form></pre>
1.33
1.34 <p>As a consequence of this form being submitted, the following parameters
1.35 will become available in the application:</p>
1.36 @@ -54,9 +47,7 @@
1.37 <p>Some limitations exist with request body parameters:</p>
1.38 <ul>
1.39 <li>For the conversion of such parameters to Unicode to function correctly,
1.40 - care must be taken with character encodings - this is discussed in <a
1.41 - href="responses.html">"Responses and Presentation"</a> and also in <a
1.42 - href="encodings.html">"Character Encodings"</a>.</li>
1.43 + care must be taken with character encodings - this is discussed in <a href="responses.html">"Responses and Presentation"</a> and also in <a href="encodings.html">"Character Encodings"</a>.</li>
1.44 </ul>
1.45
1.46 <h2>File Uploads</h2>
1.47 @@ -66,5 +57,12 @@
1.48 applications. Unlike other parameters, those which carry file upload data
1.49 expose the contents of such uploaded files as plain Python string values
1.50 instead of Unicode objects.</p>
1.51 -</body>
1.52 -</html>
1.53 +<h3>Unsupported Environments and Framework Issues</h3>
1.54 +<ul>
1.55 + <li>Twisted does not provide file upload data as raw string values;
1.56 +instead, file upload data will be decoded and returned as Unicode from
1.57 +WebStack. This behaviour is due to the way Twisted processes the
1.58 +incoming request and may be fixed in a future release.</li>
1.59 +</ul>
1.60 +
1.61 +</body></html>
1.62 \ No newline at end of file