[Seaside] Seaside 2.8 and Apache

[Richard Eng]

I managed to get it working with deployment mode, Server Port and Server
Protocol set appropriately, but now it breaks Apache's load balancer.

I think I'll just go back to Seaside 2.7. It's too much trouble trying to
get Seaside 2.8 to work (unless someone has a quick solution to load
balancing).

I should've heeded the old adage:  If it ain't broke, don't fix it. Serves
me right for being ambitious...

I was simply trying to improve performance because I like Seaside 2.8's
faster rendering speed and smaller memory footprint.

Regards,
Richard

-------
From,

http://leftshore.files.wordpress.com/2006/10/apacheandseaside.txt

SSLEngine On
SSLCertificateFile /usr/local/share/apache2/ssl/www.mydomain.com.crt
SSLCertificateKeyFile /usr/local/share/apache2/ssl/www.mydomain.com.key
SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown
ProxyRequests Off
ProxyPreserveHost On
<Proxy *>
 Order deny,allow
 Allow from none
</Proxy>
<Location /online>
 Order deny,allow
 Allow from all
 ProxyPass http://localhost:8008/online
 ProxyPassReverse http://localhost:8008/online
</Location>

Then in Smalltalk,

MyRootComponent>>install
 (self registerAsApplication: self applicationName)
   preferenceAt: #deploymentMode put: true;
   preferenceAt: #serverProtocol put: #https;
   preferenceAt: #serverPort put: 443.

-Boris

> -----Original Message-----
> From: Boris Popov
> Sent: Wednesday, November 14, 2007 8:33 AM
> To: 'Seaside - general discussion'
> Subject: RE: [Seaside] Seaside 2.8 and Apache
> 
> Did you revert the changes you did on Apache side, as you said you had
to
> change it from http://localhost:9090/seaside/fred to "https" and
that's
> not right? Then try it again and let us know.
> 
> -Boris