More information about the Underscore mailing list

[_] Plone Configuration

Oliver Humpage oliver at watershed.co.uk
Sun Jun 1 16:25:25 BST 2008

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.

Handy. Not needed if you can guarantee that every single href or src in your
site is relative, but very necessary if it's not.

> On the downside if I use <http-server>address 127.0.0.1:8080</http-server>
> it stops the above working and doesn't prevent direct port access (
> www.otherdomain.com:8080), which is a bummer.

To prevent direct port access, then make plone listen on an internal address
(like 127.0.0.1:8080). The the original directives proxying to
127.0.0.1:8080 should work.

Oliver.