Mercurial > hg > CAPTCHAmiddleware
changeset 7:8d826c3fbb06
renames in the README
| author | k0s <k0scist@gmail.com> |
|---|---|
| date | Fri, 26 Feb 2010 10:42:14 -0500 |
| parents | 015875d43b91 |
| children | 59245309f054 |
| files | README.txt |
| diffstat | 1 files changed, 5 insertions(+), 5 deletions(-) [+] |
line wrap: on
line diff
--- a/README.txt Wed Feb 24 20:29:22 2010 -0500 +++ b/README.txt Fri Feb 26 10:42:14 2010 -0500 @@ -1,13 +1,13 @@ -CAPTCHA Auth Middleware -======================= +CAPTCHA Middleware +================== -CAPTCHAauthmiddleware is a WSGI middleware python packages for putting +CAPTCHAmiddleware is a WSGI middleware python packages for putting CAPTCHAs on forms for unauthorized users (those that haven't logged in yet). If you aren't authorized -- in python terms, if remote_user is not set on the request -- then CAPTCHAs and a hidden key will be added to forms with ``method=POST``. You will be required to correctly solve the CAPTCHA in order to submit the POST request. Otherwise, the -CAPTCHAauthmiddleware will stop your request and redirect you back to +CAPTCHAmiddleware will stop your request and redirect you back to the form. @@ -53,7 +53,7 @@ then this approach might work for you. -Why does CAPTCHAauthmiddleware look half done? +Why does CAPTCHAmiddleware look half done? ---------------------------------------------- Because it is. This is very much a work in progress. Its target