Rick
unread,Jun 16, 2008, 5:37:49 PM6/16/08Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to AuthKit
I wrote some tests for my Pylons app against AuthKit 0.4.0 in which I
got the expected 401 response when the user was not logged in. I
upgraded to trunk to test the update to authkit.setup.enable so that
it enables/disables authorization in addition to authentication, but
now a 200 status is being returned with the Login Screen instead of
the previous 401. I was able to track that in revision 138 of AuthKit
trunk 401 was still being returned and in revision 139, status code
200 started being returned.
Maybe this is desired in trunk for some reason. Based on the docs I've
read I expect the 401 still. Can someone comment on this?
I see the following difference between r138 and r139 in authkit/
authenticate/form.py:
- status="200 OK",
+ status="401 Unauthorized",