www-modproxy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Gregory" <matt.greg...@skyleach.com>
Subject RE: Proxying the protocol...
Date Mon, 12 May 2003 19:53:14 GMT
Also: I have not validated Apache 2.0 for work yet.  We are still using
apache 1.3.27
-----Original Message-----
From: Juan Rivera [mailto:Juan.Rivera@citrix.com] 
Sent: Monday, May 12, 2003 9:56 AM
To: 'modproxy-dev@apache.org'
Subject: RE: Proxying the protocol...
Why don't you add your own custom header to the request?
-----Original Message-----
From: Matt Gregory [mailto:matt.gregory@skyleach.com] 
Sent: Friday, May 09, 2003 12:44 PM
To: modproxy-dev@apache.org
Subject: Proxying the protocol...
Hey all.  I have been researching and experimenting with this and have
not yet found a way to do it with either mod_rewrite or mod_proxy.
I have about 25 virtual hosts all with their own ssl keys.  I want to
proxy them all through apache to JBoss and then have JBoss proxy content
from Zope.
The problem I am having is that I have a portlet-streamer tool which I
wrote and open-sourced which will rewrite the content links from zope
according to a configuration file which works very similar to
mod_rewrite (which I used as a guide).  I have no problems except when I
try to determine what the original protocol was.
When using mod_proxy, I can use apache 2.0 and use the ProxyPreserveHost
directive to get the host from the request, or I can simply pull it from
the x-forward-host header property using my rewrite tool.  Unfortunately
nothing in the request or the header tells me if the request was via
http or via https.
Is there any way to tell the target host the original protocol via a
header variable or a directive?

View raw message