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 <email address hidden>
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
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
David Glick wrote: rrorMessage, then caught by the Publish. py's module_ standard, which resulted in calling response. exception( )...this is where PluggableAuthSe rvice's rrorMessage determines that the error_message rather than reraising the error...so that is what
> 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_standardE
> general exception handler in ZPublisher/
> publish_
> request.
> '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_standardE
> handle_errors flag is True, so it returns the rendered
> standard_
> 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. ======= ======= ======= ======= ======= ======= ======= ======= ==== palladion. com enigmail. mozdev. org
- --
=======
Tres Seaver +1 540-429-0999 <email address hidden>
Palladion Software "Excellence by Design" http://
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iD8DBQFKZIGC+ gerLs4ltQ4RAuWk AKCMiXGqU/ 2RuPA3kcLl3IOTu nemfACfQQcs LRsDvsL8=
CeO8OHzUb9LYc2m
=qsi4
-----END PGP SIGNATURE-----