summaryrefslogtreecommitdiff
path: root/paste/auth
diff options
context:
space:
mode:
authorcce <devnull@localhost>2006-01-03 00:08:13 +0000
committercce <devnull@localhost>2006-01-03 00:08:13 +0000
commit74b7bfa4b897dfd5a4ab5271cc719538b8084c56 (patch)
tree19e6a8eb8576476bb91f46d6bdec9bbf355eecfb /paste/auth
parent878e2c5afe042c4cf34a171ab631353eaa3379bb (diff)
downloadpaste-74b7bfa4b897dfd5a4ab5271cc719538b8084c56.tar.gz
Diffstat (limited to 'paste/auth')
-rw-r--r--paste/auth/cookie.py22
1 files changed, 12 insertions, 10 deletions
diff --git a/paste/auth/cookie.py b/paste/auth/cookie.py
index 2543e2f..a985f11 100644
--- a/paste/auth/cookie.py
+++ b/paste/auth/cookie.py
@@ -5,16 +5,18 @@
"""
Cookie "Saved" Authentication
-This authentication middleware saves the current REMOTE_USER and any
-other environment variables specified in a cookie so that it can be
-retrieved during the next request without requiring re-authentication.
-This uses a session cookie on the client side (so it goes away when the
-user closes their window) and does server-side expiration.
-
-Following is a very simple example where a form is presented asking
-for a user name (no actual checking), and dummy session identifier
-(perhaps corresponding to a database session id) is stored in the
-cookie.
+This authentication middleware saves the current REMOTE_USER,
+REMOTE_SESSION, and any other environment variables specified in a
+cookie so that it can be retrieved during the next request without
+requiring re-authentication. This uses a session cookie on the client
+side (so it goes away when the user closes their window) and does
+server-side expiration.
+
+Following is a very simple example where a form is presented asking for
+a user name (no actual checking), and dummy session identifier (perhaps
+corresponding to a database session id) is stored in the cookie. It
+also demonstrates the extension mechanism for storing other environment
+variables, if needed.
>>> from paste.util.httpserver import serve
>>> from paste.fileapp import DataApp