1.1 --- a/docs/parameters-headers.html Wed Aug 24 18:50:32 2005 +0000
1.2 +++ b/docs/parameters-headers.html Wed Aug 24 21:33:04 2005 +0000
1.3 @@ -1,12 +1,9 @@
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 Header 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 Header 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 <h2>Request Header Parameters</h2>
1.22 @@ -27,13 +24,9 @@
1.23
1.24 <p>Parameters encoded in this way can be written into hyperlinks and may be
1.25 used to remember things as users navigate their way around an application.
1.26 -Alternatively, a Web form (in HTML) written to use the <code>GET</code> <a
1.27 -href="methods.html">request method</a> may be used to achieve the same
1.28 +Alternatively, a Web form (in HTML) written to use the <code>GET</code> <a href="methods.html">request method</a> may be used to achieve the same
1.29 effect:</p>
1.30 -<pre><form method="GET" action="http://www.boddie.org.uk/application">
1.31 - <input name="param1" type="text" />
1.32 - <input name="param2" type="text" />
1.33 -</form></pre>
1.34 +<pre><form method="GET" action="http://www.boddie.org.uk/application"><br /> <input name="param1" type="text" /><br /> <input name="param2" type="text" /><br /></form></pre>
1.35
1.36 <div class="WebStack">
1.37 <h3>WebStack API - Accessing Header Parameters</h3>
1.38 @@ -46,7 +39,10 @@
1.39 <dt><code>get_fields_from_path</code></dt>
1.40 <dd>This returns the request parameters (fields) from the request headers
1.41 (as defined in the path or URL). The fields are provided in a
1.42 - dictionary mapping field names to lists of values</dd>
1.43 + dictionary mapping field names to lists of values<br />
1.44 +An optional <code>encoding</code> parameter may be used to assist
1.45 +the process of converting parameter values to Unicode objects - see
1.46 +below for a discussion of the issues with this parameter.</dd>
1.47 <dt><code>get_query_string</code></dt>
1.48 <dd>This returns the query string - ie. the part of the path or URL which
1.49 contains the parameters. Typically, it is easier to use the above
1.50 @@ -60,8 +56,10 @@
1.51 should remain hidden will appear in the URL and probably be shown in
1.52 browsers and other user interfaces.</li>
1.53 <li>There isn't widespread agreement about how non-ASCII characters should
1.54 - be encoded in URLs. Therefore, care must be taken to encode and decode
1.55 - values transferred in request headers.</li>
1.56 + be encoded in URLs. WebStack attempts to handle the ambiguity, but does require some assistance...</li><li>For
1.57 +the conversion of such parameters to Unicode to function correctly,
1.58 +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>.<br />
1.59 + </li>
1.60 +
1.61 </ul>
1.62 -</body>
1.63 -</html>
1.64 +</body></html>
1.65 \ No newline at end of file