Cliff Wells <[EMAIL PROTECTED]> writes:
> You don't want to know. Try lighty instead:
>
> http://www.lighttpd.net/
Just out of curiosity, how easy it is to set it up to be a "proxy" for a
normal HTTP website running on Zope (with rewrite rules on Apache) and for a
secure HTTPS website running on TG (also with rewrite rules on Apache)?
Apache is receiving the SSL connection, dealing with it and then proxying with
a plain HTTP connection inside the server.
This is the rule for the Zope website:
RewriteEngine On
RewriteRule ^/(.*)
http://localhost:8088/VirtualHostBase/http/something.my.server.com:80/Godoy/VirtualHostRoot/$1
[L,P]
This is the rule for the TG SSL website:
RewriteEngine On
RewriteRule ^/(.*) http://localhost:8080/$1 [L,P]
Zope runs on 8088, TG on 8080...
Outside these lines, very little had to be done -- mainly filling skeleton
files to have Apache configured with a nice default (one can extract more from
it if he fine tunes it, but it is not needed for this test machine).
--
Jorge Godoy <[EMAIL PROTECTED]>
