subject:"\[Zope\-dev\] Zope 2\: ZPublisher exception handling"

Re: [Zope-dev] Zope 2: ZPublisher exception handling

2010-04-14 Thread yuppie

Hi! Tres Seaver wrote: yuppie wrote: yuppie wrote: In Zope 2.10 'raise_standardErrorMessage', 'zpublisher_exception_hook' and therefore 'Publish.publish' did always (re-)raise errors after rendering. That made sure 'HTTPResponse.exception' was called and CookieCrumbler was able to hook

Re: [Zope-dev] Zope 2: ZPublisher exception handling

2010-04-13 Thread yuppie

yuppie wrote: In Zope 2.10 'raise_standardErrorMessage', 'zpublisher_exception_hook' and therefore 'Publish.publish' did always (re-)raise errors after rendering. That made sure 'HTTPResponse.exception' was called and CookieCrumbler was able to hook into 'HTTPResponse._unauthorized'. I'm now

Re: [Zope-dev] Zope 2: ZPublisher exception handling

2010-04-13 Thread Tres Seaver

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 yuppie wrote: yuppie wrote: In Zope 2.10 'raise_standardErrorMessage', 'zpublisher_exception_hook' and therefore 'Publish.publish' did always (re-)raise errors after rendering. That made sure 'HTTPResponse.exception' was called and CookieCrumbler

[Zope-dev] Zope 2: ZPublisher exception handling

2010-04-12 Thread yuppie

Hi! Summary: In Zope 2.10 'raise_standardErrorMessage', 'zpublisher_exception_hook' and therefore 'Publish.publish' did always (re-)raise errors after rendering. That made sure 'HTTPResponse.exception' was called and CookieCrumbler was able to hook into 'HTTPResponse._unauthorized'.