The Underscore Archives

On 1 Jun 2008, at 16:25, Oliver Humpage wrote:

> On 31/5/08 12:29, "Chris Keegan" <nospam at theisolationist.com> wrote:
>
>> I tried using various combinations of Oliver's suggestion but I  
>> just kept
>> getting internal server errors and couldn't figure out why. I  
>> removed the
>> ProxyPassReverse variable because I didn't really know what it  
>> did, which is
>> probably not good but I wasn't sure what the correct format was  
>> for the
>> value anyway.
>
> Say your Plone app generated links within web pages that referred  
> to itself,
> e.g. <a href="http://127.0.0.1:8080/path/to/page">. ProxyPassReverse
> rewrites those links to point to your own server, so the user sees  
> the link
> as http://plone.mydomain.com/path/to/page.

Actually, that is not quite true.  AFAIK ProxyPassReverse doesn't do  
anything to the HTML being proxied through.  It is used when the  
apache server *itself* needs to construct a URL, it knows what the  
base should be.  This is normally for things like redirecting if  
there is a missing trailing slash and the likes.

The way (for Plone) you get the links in the HTML to agree with the  
hostname (ie plone.mydomain.com v.s. 127.0.0.1) is by the complicated  
rewrite URL which has the hostname and port encoded in it.

-Matt

-- 
Matt Hamilton                                       matth at netsight.co.uk
Netsight Internet Solutions, Ltd.           Understand. Develop. Deliver
http://www.netsight.co.uk                             +44 (0)117 9090901
Web Design | Zope/Plone Development & Consulting | Co-location | Hosting