23-Jul-99 09:03 you wrote:
> Hi Ralf,
> it's me again. I don't understand the use of ap_hook_use and how it would
> solve my problem. In my modules "URI to filename translation" phase I'd like
> to call the ssl's module handler "ssl_hook_fixup" which is setting up all
> SSL variables so the would be availbale to me immediately after the call to
> ssl_hook_fixup returns. Is there a way to do that right now?
No. Not easy, anyway...
> I read the documentation provided in ap_hook.c but I don't understand the
> workings I also would appreciate a short explanation of how ap_hook_use
> works. Must the hook specified in ap_hook_use be configured and registered
> in mod_ssl before it can be used?
No. You just call hook "ap::mod_rewrite::lookup_variable" to find out varible
value instead of standard Apache way. That's all. What's so problematic here ???
Why you are so inclined to setting up SSL variables ?
> Thanks a lot for your help.
> Arnold
> -----Original Message-----
> From: Ralf S. Engelschall [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, July 22, 1999 2:17 AM
> To: [EMAIL PROTECTED]
> Subject: Re: SSL variables running APACHE on Windows NT 4.0
> On Mon, Jul 19, 1999, Ruetzel, Arnold wrote:
>> I wrote my own module which is loaded by Apache at startup time. This
> module
>> has to access the SSL variables in the "URI to filename translation"
> phase,
>> but the variables are not available at this phase. Does anybody know what
> I
>> have to do to make the SSL variables available to me in the "URI to
> filename
>> translation" phase ? Is there a way to make use of mod_ssl's API's to get
> my
>> hands on the SSL variables and how would that be done?
> When you looked into mod_rewrite, you would have found:
> #ifdef EAPI
> ap_hook_use("ap::mod_rewrite::lookup_variable",
> AP_HOOK_SIG3(ptr,ptr,ptr),
> AP_HOOK_DECLINE(NULL),
> &result, r, var);
> #endif
> A similar call in your module will give you the results.
>> PS: A note for Ralf Engelschall: Do you have any plans to change mod_ssl
> to
>> make the SSL variables available right from the start, that is before the
>> post_read_request or header_parser handlers are being called.
> Hmmm... mod_ssl currently does it in the "correct/intended" phase. But
> sure,
> it shouldn't harm to provide them earlier. I've to admit that I currently
> forgot what the reason was that have not done this already. I'll think about
> this again....
> Ralf S. Engelschall
> [EMAIL PROTECTED]
> www.engelschall.com
> ______________________________________________________________________
> Apache Interface to OpenSSL (mod_ssl) www.modssl.org
> User Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
> ______________________________________________________________________
> Apache Interface to OpenSSL (mod_ssl) www.modssl.org
> User Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
