1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/docs/redirection.html Wed Nov 16 18:27:45 2005 +0000
1.3 @@ -0,0 +1,18 @@
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"><head>
1.6 + <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type" />
1.7 +
1.8 + <title>Redirection</title><meta name="generator" content="amaya 8.1a, see http://www.w3.org/Amaya/" />
1.9 + <link href="styles.css" rel="stylesheet" type="text/css" /></head>
1.10 +
1.11 +<body>
1.12 +<h1>Redirection</h1><p>Instead of presenting information to a user when
1.13 +that user visits a particular URL, we may instead choose to redirect
1.14 +that user to another URL, at which there may be information to be
1.15 +viewed. To redirect a user of an application, we can use the following
1.16 +transaction method:</p><div class="WebStack">
1.17 +<h3>WebStack API - Redirection</h3>
1.18 +<p>WebStack provides the following method to perform redirection:</p>
1.19 +<dl><dt><code>redirect</code></dt><dd>This method accepts a path value
1.20 +suitable for use in response headers indicating the location to which a
1.21 +user shall be redirected. An optional response code (see <a href="responses.html">"Responses and Presentation"</a>) can be specified to modify the meaning of the redirection (as defined in the HTTP specifications).</dd></dl></div><p>Since the path value must be usable in response header, it is necessary to transform paths as described in the <a href="path-value-encoding.html">"Encoding and Decoding Path Values"</a> document, and an example of redirection is given in that document.</p></body></html>
1.22 \ No newline at end of file