From b3255290e96d2b9551516c8f8306ee787adf8fb6 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Sun, 10 Apr 2011 16:03:07 -0400 Subject: - It is now possible to get information about why Pyramid raised a Forbidden exception from within an exception view. The ``ACLDenied`` object returned by the ``permits`` method of each stock authorization policy (``pyramid.interfaces.IAuthorizationPolicy.permits``) is now attached to the Forbidden exception as its ``result`` attribute. Therefore, if you've created a Forbidden exception view, you can see the ACE, ACL, permission, and principals involved in the request as eg. ``context.result.permission``, ``context.result.acl``, etc within the logic of the Forbidden exception view. --- TODO.txt | 3 --- 1 file changed, 3 deletions(-) (limited to 'TODO.txt') diff --git a/TODO.txt b/TODO.txt index 07e74ba0d..d8e6dcdac 100644 --- a/TODO.txt +++ b/TODO.txt @@ -32,9 +32,6 @@ Should-Have - Provide a response_set_cookie method on the request for rendered responses that can be used as input to response.set_cookie? -- Make it possible to get at ACLDenied data from Forbidden response in - exceptionview. - Nice-to-Have ------------ -- cgit v1.2.3