How to preserve all request headers in reverse proxy (mod_proxy)

--0015175ccf7a9c73c5047af01fa9
Content-Type: text/plain; charset=ISO-8859-1

Hi all:

In httpd 2.2, is it possible to preserve all HTTP headers when using
mod_proxy to provide a reverse proxy?

Here's my desired setup: I'm running two domains on one server backed by one
Tomcat instance. I'm trying to run httpd as a reverse proxy to send
http://www.domain1.com/... to http://localhost:8080/domain1/... and
http://www.domain2.com/... to http://localhost:8080/domain2/... (with HTTPS
traffic going to port 8443). Starting to play with this, I've set up the
following config:

ProxyRequests Off


Order deny,allow
Allow from all


ProxyPass / http://localhost:8080/domain1/
ProxyPassReverse / http://localhost:8080/domain1/

However, the request headers are being lost in the process. I'd like to
keep them all in tact. Is there any way to accomplish this? The
"ProxyPreserveHost" works for the host header, but what about the rest?

Thanks for the help!
-T

--0015175ccf7a9c73c5047af01fa9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all:

In httpd 2.2, is it possible to preserve all HTTP headers wh=
en using mod_proxy to provide a reverse proxy?

Here's my desired=
setup: I'm running two domains on one server backed by one Tomcat inst=
ance.=A0 I'm trying to run httpd as a reverse proxy to send http://www.domain1.com/.">http://www.domain1.com/... to ://localhost:8080/domain1/.">http://localhost:8080/domain1/... and ref=3D"http://www.domain2.com/.">http://www.domain2.com/... to =3D"http://localhost:8080/domain2/.">http://localhost:8080/d omain2/... =
(with HTTPS traffic going to port 8443).    Starting to play with this,=
I've set up the following config:


ProxyRequests Off

<Proxy *>
  =A0 Order deny,allow<=
br>  =A0 Allow from all
</Proxy>

ProxyPass / "http://localhost:8080/domain1/">http://localhost:8080/domai n1/
Prox=
yPassReverse / http://localhost:=
8080/domain1/


However, the request headers are being lost in the process.=A0 I'd =
like to keep them all in tact.=A0 Is there any way to accomplish this?=A0 T=
he "ProxyPreserveHost" works for the host header, but what about =
the rest?


Thanks for the help!
-T



--0015175ccf7a9c73c5047af01fa9--

Re: How to preserve all request headers in reverse proxy (mod_proxy)

--00032555ae56f874d3047af4789b
Content-Type: text/plain; charset=ISO-8859-1

Actually, I'm not even sure what I'm trying to do is possible - can someone
confirm that I'm attempting something that can be done? :)

Basically, I have foo.war and bar.war and own the foo.com and
bar.comdomains. I want to deploy the two web-apps in Tomcat on port
8080 and have
httpd send http://www.foo.com/ to http://localhost:8080/foo/ and
http://www.bar.com/ to http://localhost:8080/bar/ so that each web-app looks
like its own top-level web-app in its own domain. Is this doable, 'cause I
can't seem to find anyone out there who's done it :)

-T

On Thu, Dec 17, 2009 at 12:40 PM, Todd Volkert wrote:

> Hi all:
>
> In httpd 2.2, is it possible to preserve all HTTP headers when using
> mod_proxy to provide a reverse proxy?
>
> Here's my desired setup: I'm running two domains on one server backed by
> one Tomcat instance. I'm trying to run httpd as a reverse proxy to send
> http://www.domain1.com/... to http://localhost:8080/domain1/... and
> http://www.domain2.com/... to http://localhost:8080/domain2/... (with
> HTTPS traffic going to port 8443). Starting to play with this, I've set
> up the following config:
>
> ProxyRequests Off
>
>
> Order deny,allow
> Allow from all
>
>
> ProxyPass / http://localhost:8080/domain1/
> ProxyPassReverse / http://localhost:8080/domain1/
>
> However, the request headers are being lost in the process. I'd like to
> keep them all in tact. Is there any way to accomplish this? The
> "ProxyPreserveHost" works for the host header, but what about the rest?
>
> Thanks for the help!
> -T
>
>

--00032555ae56f874d3047af4789b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Actually, I'm not even sure what I'm trying to do is possible - can=
someone confirm that I'm attempting something that can be done? :)
=

Basically, I have foo.war and bar.war and own the ..com">foo.com and domains.=A0 I =
want to deploy the two web-apps in Tomcat on port 8080 and have httpd send =
to //localhost:8080/foo/">http://localhost:8080/foo/ and /www.bar.com/">http://www.bar.com/ to bar/">http://localhost:8080/bar/ so that each web-app looks like its ow=
n top-level web-app in its own domain.=A0 Is this doable, 'cause I can&=
#39;t seem to find anyone out there who's done it :)


-T

Re: Re: How to preserve all request headers in reverseproxy (mod_proxy)

Todd Volkert wrote:
> Actually, I'm not even sure what I'm trying to do is possible - can
> someone confirm that I'm attempting something that can be done? :)
>
> Basically, I have foo.war and bar.war and own the foo.com
> and bar.com domains. I want to deploy
> the two web-apps in Tomcat on port 8080 and have httpd send
> http://www.foo.com/ to http://localhost:8080/foo/ and
> http://www.bar.com/ to http://localhost:8080/bar/ so that each web-app
> looks like its own top-level web-app in its own domain. Is this doable,
> 'cause I can't seem to find anyone out there who's done it :)

What's the problem?

The rules for which request headers are passed through are determined
by the HTTP standard, not by Apache. In some cases you have choices,
documented in the mod_proxy_http page.

If you tell us what's really the problem, maybe someone can help.

--
Nick Kew

------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: Re: How to preserve all request headers in reverse

--00032555d43e5c9fc4047af4e281
Content-Type: text/plain; charset=ISO-8859-1

Haha - the problem is I'm an idiot :) Your message made me go back and
check my assumptions, and sure enough, I took stupid pills today.

I had created a test page that spits out the request headers in HTML, and I
checked the page in Firefox bypassing the proxy, then checked it *by
telnetting to port 80* using the proxy. Of course there were no user-agent
request headers when I used telnet! I saw the lack of request headers and
thought "the proxy is dropping them!"

,
-T

On Thu, Dec 17, 2009 at 6:01 PM, Nick Kew wrote:

> Todd Volkert wrote:
>
>> Actually, I'm not even sure what I'm trying to do is possible - can
>> someone confirm that I'm attempting something that can be done? :)
>>
>> Basically, I have foo.war and bar.war and own the foo.com
>> and bar.com domains. I want to deploy the two web-apps
>> in Tomcat on port 8080 and have httpd send http://www.foo.com/ to
>> http://localhost:8080/foo/ and http://www.bar.com/ to
>> http://localhost:8080/bar/ so that each web-app looks like its own
>> top-level web-app in its own domain. Is this doable, 'cause I can't seem to
>> find anyone out there who's done it :)
>>
>
> What's the problem?
>
> The rules for which request headers are passed through are determined
> by the HTTP standard, not by Apache. In some cases you have choices,
> documented in the mod_proxy_http page.
>
> If you tell us what's really the problem, maybe someone can help.
>
> --
> Nick Kew
>
> ------------------------------------------------------------ ---------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>

--00032555d43e5c9fc4047af4e281
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Haha - the problem is I'm an idiot :)=A0 Your message made me go back a=
nd check my assumptions, and sure enough, I took stupid pills today.
>I had created a test page that spits out the request headers in HTML, and =
I checked the page in Firefox bypassing the proxy, then checked it *by teln=
etting to port 80* using the proxy.=A0 Of course there were no user-agent r=
equest headers when I used telnet!=A0 I saw the lack of request headers and=
thought "the proxy is dropping them!"


<sheepish-grin/>,
-T