> > > -----Original Message----- > > From: Bill Stoddard [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, February 12, 2002 10:41 AM > > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > > Subject: Re: adding another hook to proxy-http > > > > > > I think everything Ryan has suggested is goodness, but we > > still have a conundrum.... > > > > proxy_http must call ap_run_pre_connection() to install > > CORE_IN/CORE_OUT (and set up the > > core_net_rec). However, we really should not call > > ap_run_pre_connection() because it's not > > valid for all the loaded modules to install their default > > front end filters into the > > backend connection. > > > > A couple of solutions: > > 1. Each module becomes aware of how their hook is being used, > > to install front-end or > > back-end filters (Yech). > > > > 2. We need to architect a new hook in Apache to give modules > > the opportunity to install > > backend filters, maybe named ap_run_proxy_install_filters() > > or something like that. Most > > modules will not use it (obviously mod_proxy would). core.c > > would need to implement the > > hook to install default in/out filters (CORE_IN/CORE). > > hmm.. > I was thinking that the hook could be self-contained in mod_proxy.c > with no inolvement of core.c or others. > things which want to do something to the proxy would include mod_proxy.h >
But we need CORE_IN and CORE which today can only be installed via the pre_connection hook. And running pre_connection on the back-end connection is not good. Right? Bill
