[K12OSN] OT: Reverse proxy for internal websites

Les Mikesell les at futuresource.com
Mon Jan 14 00:34:40 UTC 2008


David Hopkins wrote:
>> You can't do named virtual hosts for https (proxied or not) because the
>> Host: header needed to identify the named site will be encrypted and you
>> need to know the host to use the right certificate to match up.  You'll
>> always hit the default host regardless of the name passed.  You can do
>> it with IP or port based virtual hosts - but then you might as well
>> port-forward.
>>
> 
> Did not know this ... thanks.  The scenario that I saw used was https
> to the Apache reverse proxy and then plain http from the Apache proxy
> to the OWA. Is that the point of SSL-offloading?

Yes, you can accept https and proxy to an http backend, you just can't 
handle more than one site on the same ip/port because you can't see the 
name from the host header at the time you need it.

-- 
   Les Mikesell
    lesmikesell at gmail.com




More information about the K12OSN mailing list