paulb@507 | 1 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
paulb@507 | 2 | <html xmlns="http://www.w3.org/1999/xhtml"><head> |
paulb@507 | 3 | <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type" /> |
paulb@507 | 4 | |
paulb@507 | 5 | <title>Redirection</title><meta name="generator" content="amaya 8.1a, see http://www.w3.org/Amaya/" /> |
paulb@507 | 6 | <link href="styles.css" rel="stylesheet" type="text/css" /></head> |
paulb@507 | 7 | |
paulb@507 | 8 | <body> |
paulb@507 | 9 | <h1>Redirection</h1><p>Instead of presenting information to a user when |
paulb@507 | 10 | that user visits a particular URL, we may instead choose to redirect |
paulb@507 | 11 | that user to another URL, at which there may be information to be |
paulb@507 | 12 | viewed. To redirect a user of an application, we can use the following |
paulb@507 | 13 | transaction method:</p><div class="WebStack"> |
paulb@507 | 14 | <h3>WebStack API - Redirection</h3> |
paulb@507 | 15 | <p>WebStack provides the following method to perform redirection:</p> |
paulb@507 | 16 | <dl><dt><code>redirect</code></dt><dd>This method accepts a path value |
paulb@507 | 17 | suitable for use in response headers indicating the location to which a |
paulb@507 | 18 | 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> |