httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom Evans <tevans...@googlemail.com>
Subject Re: [users@httpd] Apache Reverse Proxy & Caching configuration for HTTPS
Date Thu, 22 Nov 2012 12:33:21 GMT
On Thu, Nov 22, 2012 at 12:02 PM, Igor Galić <i.galic@brainsware.org> wrote:
>
>
> ----- Original Message -----
>> Hi Friends,
>>
>> I have the below Reverse Proxy setup. I am also doing caching for a
>> few folders which serve static content.
>> It is working fine for HTTP URLs.
>>
>> I have to now enable this proxy approach for HTTPS on both URLs. I
>> will now have https://mysite.com and https://mysite.intranet.com.
>> Is there any guide available which can help with the steps required?
>> Will the below configuration need changes for HTTPS proxy or HTTPS
>> caching?
>
> No. Caching for HTTP is no different from caching for HTTPS, when
> httpd does the termination.
>
> Here's some general notes, though:
>
>> <VirtualHost 1.2.3.4:80>
>>     ServerName mysite.com
>>       ProxyPass / http://mysite.intranet. com/
>>       ProxyPassReverse / http://mysite.intranet. com/
>>       ProxyPassReverse / http://mysite.intranet. com:80/
>
> That doesn't work, you only can have one reverse path.
> http:// implies :80

I'm not sure this is correct. You can specify any number of
ProxyPassReverse that you like, you are not limited to one reverse
path.

ProxyPassReverse also only operates as string replacement, it does not
magically infer port numbers if not specified in the directive.

Eg, with this:

ProxyPassReverse / http://mysite/

and a response is proxied with the location header
"http://mysite:80/foo/bar", then it will not be rewritten.

Cheers

Tom

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message