Author: buildbot
Date: Sun Apr 22 18:37:36 2012
New Revision: 813992
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/authentication---framework.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Apr 22 18:37:36 2012
@@ -1 +1 @@
-1328927
+1328928
Modified: websites/staging/sling/trunk/content/authentication---framework.html
==============================================================================
--- websites/staging/sling/trunk/content/authentication---framework.html
(original)
+++ websites/staging/sling/trunk/content/authentication---framework.html Sun
Apr 22 18:37:36 2012
@@ -294,10 +294,28 @@ path at all are not called.</li>
is assumed credentials have been requested from the client.</li>
</ol>
<p>The <em>login</em> method has three possible exit states:</p>
-<p>|| Exit State || Description ||
-| Normal | An <code>AuthenticationHandler</code> could be selected to which
the login request could be forwarded. |
-| <code>NoAuthenticationHandlerException</code> | No
<code>AuthenticationHandler</code> could be selected to forward the login
request to. In this case, the caller can proceed as appropriate. For example a
servlet, which should just login a user may send back a 403/FORBIDDEN status
because login is not possible. Or a 404/NOT FOUND handler, which tried to login
as a fallback, may continue and send back the regular 404/NOT FOUND response. |
-| <code>IllegalStateException</code> | The response has already been committed
and the login request cannot be processed. Normally to request login, the
current response must be reset and a new response has to be prepared. This is
only possible if the request has not yet been committed. |</p>
+<table>
+<thead>
+<tr>
+<th>Exit State</th>
+<th>Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>Normal</td>
+<td>An <code>AuthenticationHandler</code> could be selected to which the login
request could be forwarded.</td>
+</tr>
+<tr>
+<td><code>NoAuthenticationHandlerException</code></td>
+<td>No <code>AuthenticationHandler</code> could be selected to forward the
login request to. In this case, the caller can proceed as appropriate. For
example a servlet, which should just login a user may send back a 403/FORBIDDEN
status because login is not possible. Or a 404/NOT FOUND handler, which tried
to login as a fallback, may continue and send back the regular 404/NOT FOUND
response.</td>
+</tr>
+<tr>
+<td><code>IllegalStateException</code></td>
+<td>The response has already been committed and the login request cannot be
processed. Normally to request login, the current response must be reset and a
new response has to be prepared. This is only possible if the request has not
yet been committed.</td>
+</tr>
+</tbody>
+</table>
<p><strong>logout</strong>
1. Select one or more <em>AuthenticationHandler</em> for the request according
to the request URL's scheme and authorization part.
