Re: HTTP_X_FORWARDED_HOST breaks Apache proxying


#1

Earl C. removed_email_address@domain.invalid wrote:The problem is that when Apache
forwards the request using proxypass, it includes the following in the
HTML:


HTTP_X_FORWARDED_HOST: foo
HTTP_USER_AGENT: Wget/1.10.2 (Red Hat modified)
SCRIPT_NAME: /
SERVER_PROTOCOL: HTTP/1.1
HTTP_HOST: 127.0.0.1:3000

There is a patch for Apache to add ProxyAddXHeaders:

http://mail-archives.apache.org/mod_mbox/httpd-dev/200702.mbox/browser

Setting this option Off causes Apache to refrain from inserting the
HTTP_X_* headers making the proxying action transparent.


Need Mail bonding?
Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users.


#2

On 02/06/07 01:00 AM, Earl C. was heard to say:

Earl C. removed_email_address@domain.invalid wrote:The problem is that when Apache forwards the request using proxypass, it includes the following in the HTML:


HTTP_X_FORWARDED_HOST: foo
HTTP_USER_AGENT: Wget/1.10.2 (Red Hat modified)
SCRIPT_NAME: /
SERVER_PROTOCOL: HTTP/1.1
HTTP_HOST: 127.0.0.1:3000

Hi Earl,

the Apache headers are fine and are supposed to be set this way. The
problem is that Radiant/Rails does not know what the base URL of your
application is. Try setting:

ActionController::AbstractRequest.relative_url_root = ‘/radiant’

in your environment.rb. I am not sure if this is still the right way
of doing it, but it used to be like this a couple of months ago.

Cheers,
Oliver