1.1 --- a/docs/headers.html Sat Sep 08 16:01:41 2007 +0000
1.2 +++ b/docs/headers.html Sat Sep 08 16:02:18 2007 +0000
1.3 @@ -1,21 +1,19 @@
1.4 +<?xml version="1.0" encoding="iso-8859-1"?>
1.5 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
1.6 <html xmlns="http://www.w3.org/1999/xhtml"><head>
1.7 <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type" />
1.8 -
1.9 -
1.10 - <title>Request Headers</title><meta name="generator" content="amaya 8.1a, see http://www.w3.org/Amaya/" />
1.11 + <title>Request Headers</title>
1.12 <link href="styles.css" rel="stylesheet" type="text/css" /></head>
1.13 <body>
1.14 <h1>Request Headers</h1>
1.15
1.16 -
1.17 <p>Request headers are pieces of information that describe certain aspects of a request, such as:</p>
1.18 <ul>
1.19 <li>The location to which the request is being sent.</li>
1.20 <li>The type of information in the request body.</li>
1.21 <li>Preferences about which kinds of information the sender would like to receive in return.</li>
1.22 </ul>
1.23 -<p>The location and related query information is conveniently accessible through <a href="paths.html">path</a> information and <a href="parameters-headers.html">request header parameter</a> information. Other types of header information are made available through other WebStack API methods.</p>
1.24 +<p>The location and related query information is conveniently accessible through <a href="paths.html">path</a> information and <a href="parameters-headers.html">request header parameter</a> information. Other types of header information are made available through other WebStack API methods.</p>
1.25 <h2>Content Types</h2>
1.26 <p>When a Web application sends some information in a response, it
1.27 describes the content type of that information, and this is described
1.28 @@ -28,7 +26,7 @@
1.29
1.30 <p>Unfortunately, such information is not always provided by Web browsers.</p>
1.31 <h2>Content Preferences</h2>
1.32 -<p>Sometimes, Web browsers describe the kinds of information that
1.33 +<p>Sometimes, Web browsers describe the kinds of information that
1.34 they are willing to receive, and WebStack provides various means to
1.35 query such preferences:</p>
1.36
1.37 @@ -52,7 +50,7 @@
1.38 </dd>
1.39 <dt><code>get_header_values</code></dt>
1.40 <dd>Given a header name as parameter, this method returns a list of string values associated with that name.</dd><dt><code>get_content_type</code></dt>
1.41 - <dd>This returns a content type object (typically <code>WebStack.Generic.ContentType</code>) describing the incoming request body content.</dd>
1.42 + <dd>This returns a content type object (typically <code>WebStack.Generic.ContentType</code>) describing the incoming request body content.</dd>
1.43 <dt><code>get_content_languages</code></dt>
1.44 <dd>This returns a list of language identifiers, in descending order
1.45 of preference, indicating in which languages the sender of the request
1.46 @@ -63,8 +61,8 @@
1.47 the request would prefer to receive information.</dd>
1.48
1.49 </dl>
1.50 -<p>It should be noted that the <code>get_headers</code> and <code>get_header_values</code> methods
1.51 +<p>It should be noted that the <code>get_headers</code> and <code>get_header_values</code> methods
1.52 present a slightly different view of the available header information,
1.53 -in that only a single header value is made available through the <code>get_headers</code> method for each header name, whereas <code>get_header_values</code> provides potentially many values for the same header name. </p>
1.54 +in that only a single header value is made available through the <code>get_headers</code> method for each header name, whereas <code>get_header_values</code> provides potentially many values for the same header name. </p>
1.55
1.56 -</div></body></html>
1.57 \ No newline at end of file
1.58 +</div></body></html>