Chris McDonough
2011-01-25 d3a028f3eab91f9bb26761af59fa1d71085a2921
add example of reconfiguring challenge decider for r.who users
1 files modified
10 ■■■■■ changed files
docs/whatsnew-1.0.rst 10 ●●●●● patch | view | raw | blame | history
docs/whatsnew-1.0.rst
@@ -412,7 +412,15 @@
  cause problems for users of Pyramid with :mod:`repoze.who`, which
  intercepts ``401 Unauthorized`` by default, but allows ``403 Forbidden`` to
  pass through.  Those deployments will need to configure :mod:`repoze.who`
  to also react to ``403 Forbidden``.
  to also react to ``403 Forbidden``.  To do so, use a repoze.who
  ``challenge_decider`` that looks like this::
     import zope.interface
     from repoze.who.interfaces import IChallengeDecider
     def challenge_decider(environ, status, headers):
         return status.startswith('403') or status.startswith('401')
     zope.interface.directlyProvides(challenge_decider, IChallengeDecider)
- The ``paster bfgshell`` command is now known as ``paster pshell``.