Re: is postreadrequest too late to determine name vhost?

2001-08-29 Thread Vivek Khera
TE == Thomas Eibner [EMAIL PROTECTED] writes: TE It seems that everything concerning vhosts is set up in http_protocal.c TE and that the vhost is set right after Apache has read the request from TE the client and then calling ap_update_vhost_from_headers to actually TE determine the vhost. All

Re: is postreadrequest too late to determine name vhost?

2001-08-29 Thread Thomas Eibner
On Wed, Aug 29, 2001 at 02:44:48PM -0400, Vivek Khera wrote: TE == Thomas Eibner [EMAIL PROTECTED] writes: TE It seems that everything concerning vhosts is set up in http_protocal.c TE and that the vhost is set right after Apache has read the request from TE the client and then calling

is postreadrequest too late to determine name vhost?

2001-08-29 Thread Vivek Khera
I've got the classic lightweight front end proxying to the mod_perl heavyweight backend. I use proxy_add_forward on the front end and the PerlPostReadRequest handler to set $r-hostname and $r-remote_ip. This all works excellently. My question, however, is this too late for the name-based

Re: is postreadrequest too late to determine name vhost?

2001-08-29 Thread Thomas Eibner
On Wed, Aug 29, 2001 at 01:31:54PM -0400, Vivek Khera wrote: I've got the classic lightweight front end proxying to the mod_perl heavyweight backend. I use proxy_add_forward on the front end and the PerlPostReadRequest handler to set $r-hostname and $r-remote_ip. This all works