[zope2-tracker] [Bug 372632] Re: zope 2.12.0b1 does not use standard_error_message

[Tres Seaver]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David Glick wrote:
> There is still a regression in this code compared to 2.10.  In 2.10, an
> Unauthorized exception raised while publishing an object ended up being
> re-raised by SimpleItem's raise_standardErrorMessage, then caught by the
> general exception handler in ZPublisher/Publish.py's
> publish_module_standard, which resulted in calling
> request.response.exception()...this is where PluggableAuthService's
> 'challenge' plugin hooks in, which is the mechanism by which, in Plone
> at least, accessing an unauthorized object results in a redirection to
> the login screen.
> 
> In Zope 2.12.0b3, raise_standardErrorMessage determines that the
> handle_errors flag is True, so it returns the rendered
> standard_error_message rather than reraising the error...so that is what
> the response renders and it never gets a chance to process the
> exception.
> 
> I don't understand the purpose of why the handle_errors flag was added
> in the first place, so I'm having a hard time figuring out the correct
> way to test and resolve this.  Can anyone shed some light on it?

I think Hanno's recent changes have fixed this regression.  David, can
you test against the 2.12 branch and the trunk?


Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFKZIGC+gerLs4ltQ4RAuWkAKCMiXGqU/2RuPA3kcLl3IOTunemfACfQQcs
CeO8OHzUb9LYc2mLRsDvsL8=
=qsi4
-----END PGP SIGNATURE-----

-- 
zope 2.12.0b1 does not use standard_error_message
https://bugs.launchpad.net/bugs/372632
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.