diff options
| author | Chris McDonough <chrism@plope.com> | 2011-04-10 16:03:07 -0400 |
|---|---|---|
| committer | Chris McDonough <chrism@plope.com> | 2011-04-10 16:03:07 -0400 |
| commit | b3255290e96d2b9551516c8f8306ee787adf8fb6 (patch) | |
| tree | 7671d60fa68202d8b1e99d7516e3522b8a9b13fb /docs | |
| parent | 4d1602230db7b1274fd7fff43764c46a6e52b83b (diff) | |
| download | pyramid-b3255290e96d2b9551516c8f8306ee787adf8fb6.tar.gz pyramid-b3255290e96d2b9551516c8f8306ee787adf8fb6.tar.bz2 pyramid-b3255290e96d2b9551516c8f8306ee787adf8fb6.zip | |
- 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.
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions