Graham,
I think what he means is if he's RPing a site (http://a/) and his app
is coded to check the host_header value (if host == a) to see how it
should behave. While that coding style is questionable, perhaps it's
necessary for some reason.
The way we have done it at one of my clients is to set up a /etc/hosts
with hostname b and the destination ip. Then config the ProxyPass to
that name (http://b/). So at least they get a hostname they can track
without too much recoding of the web app. I was hoping for something
better than that, so I was trying to wait for a response. :) Was hoping
you could artificially populate the host header variable to the "real"
web server. But I haven't found any way to do that. There is a
variable X-forwarded-host and x-forwarded-server that both seem to
represent host a (the original request from the browser). Is this
accurate?
Geff
On Wed, 2003-02-12 at 08:37, Graham Leggett wrote:
> Manon Goo wrote:
>
> > Is there any possibility to tell the realserver whct the hostname is ?
>
> What do you mean by "real server" and "hostname"?
>
> > I want to use ProxyPass /x http://10.1.1.1/
> >
> > but I want to send "backendserver" in the HTTP Header to the host
>
> Use the "Header" directive to add arbitrary headers in the response to
> the browser.
>
> If you want the backend server to know the IP address of the browser,
> look for the X-Forwarded-For header.
>
> Regards,
> Graham
> --
> -----------------------------------------
> [EMAIL PROTECTED] "There's a moon
> over Bourbon Street
> tonight..."
>
