> Am 23.09.2015 um 14:09 schrieb Eric Covener <[email protected]>: > > On Wed, Sep 23, 2015 at 7:40 AM, Stefan Eissing > <[email protected]> wrote: >> The question then is how we best let other modules stop ssl_hook_Access() >> from performing >> the renegotiation. It may then return HTTP_FORBIDDEN. Then denying hook >> could store context >> information in r->notes so that the request is answered specific to the >> protocols need. >> >> Another hook in core which ssl_hook_Access() then triggers? > > optional function exported by mod_ssl to block renegotiation?
Needs to register a callback and needs to be able to handle more than one. Smells like a hook, at least internally. Nothing against an optional function for registration... <green/>bytes GmbH Hafenweg 16, 48155 Münster, Germany Phone: +49 251 2807760. Amtsgericht Münster: HRB5782
