svn commit: r1328925 - /sling/site/trunk/content/authentication---framework.mdtext

[fm...@apache.org]

Author: fmeschbe
Date: Sun Apr 22 18:28:53 2012
New Revision: 1328925

URL: http://svn.apache.org/viewvc?rev=1328925&view=rev
Log:
authentication page improvements

Modified:
    sling/site/trunk/content/authentication---framework.mdtext

Modified: sling/site/trunk/content/authentication---framework.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/authentication---framework.mdtext?rev=1328925&r1=1328924&r2=1328925&view=diff
==============================================================================
--- sling/site/trunk/content/authentication---framework.mdtext (original)
+++ sling/site/trunk/content/authentication---framework.mdtext Sun Apr 22 18:28:53 2012
@@ -113,8 +113,9 @@ versions of the Sling Commons Auth bundl
 be present anymore. To get the JCR Session for the current request adapt
 the request's resource resolver to a JCR Session:
 
-
-    Session session = request.getResourceResolver().adaptTo(Session.class);
+~~~~~~
+Session session = request.getResourceResolver().adaptTo(Session.class);
+~~~~~~
 
 
 
@@ -188,21 +189,10 @@ is assumed credentials have been request
 
 The *login* method has three possible exit states:
 
-<table>
-<tr><th> Exit State </th><th> Description </th></tr>
-<tr><td> Normal </td><td> An *AuthenticationHandler* could be selected to which the
-login request could be forwarded. </td></tr>
-<tr><td> *NoAuthenticationHandlerException* </td><td> No *AuthenticationHandler* 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> *IllegalStateException* </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>
-</table>
+|| Exit State || Description ||
+| Normal | An `AuthenticationHandler` could be selected to which the login request could be forwarded. |
+| `NoAuthenticationHandlerException` | No `AuthenticationHandler` 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. |
+| `IllegalStateException` | 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. |
 
 
 **logout**