John,
That is helpful. I have read elsewhere about avoiding rewrite in
Seaside setups, and will do some searching with that in mind. After a
couple of tries, I turned up an exampled you posted earlier (see below).
My (perhaps errant) assumption has been that the rewrite rules were
needed to fix up the protocol. Any comments on whether the virtual host
below is/can/cannot be secure would be appreciated.
Thanks,
Bill
<VirtualHost *:80>
#I've removed web address,
ServerName xxx.xxx.xxx #normally this would be a domain
#such as www.google.com
ProxyRequests Off
ProxyPreserveHost On
<Location /files>
ProxyPass
http://127.0.0.1:9090/seaside/files/FVFiles/
ProxyPassReverse
http://127.0.0.1:9090/seaside/files/FVFiles/
</Location>
<Location /images>
ProxyPass !
</Location>
<Location /tinymce>
ProxyPass !
</Location>
<Location />
ProxyPass
http://127.0.0.1:9091/seaside/fv/
ProxyPassReverse
http://127.0.0.1:9091/seaside/fv/
</Location>
</VirtualHost>
Wilhelm K. Schwab, Ph.D.
University of Florida
Department of Anesthesiology
PO Box 100254
Gainesville, FL 32610-0254
Email:
[hidden email]
Tel: (352) 273-6785
FAX: (352) 392-7029
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside