-----Original Message----- From: Jens Vagelpohl [mailto:jens@zope.com] Sent: Thursday, August 28, 2003 9:06 AM To: Tiller, Michael (M.M.) Cc: zope@zope.org Subject: Re: [Zope] Can't build resource file for PCGI on Zope 2.7b1
If PCGI is gone, how can we accomplish the same thing without opening up a port? I don't doubt that "[PCGI] is almost never an appropriate solution", but I cannot seem to figure out what is an appropriate solution in our case.
Very simple if the frontend webserver sits on the same machine: Have Zope listen on a port on localhost only. Then your frontend server simply redirects/rewrites/whatever to that port on localhost. Thus Zope won't be reachable on any external interface.
Ah...good point. Thanks for reminding me. That is a step in the right direction. BUT, it still seems to me that it isn't as good a named pipe (although I'd be glad to be proven wrong) because with a named pipe *you can control the permissions of the pipe* whereas anyone can connect to the localhost port if they have an account on the machine. Am I missing something again? :-)
jens
-- Mike