Reverse Proxy setup for Apache2 for use w/ Seaside apps.. (was: Re: [Q] FastCGI + Squeak?)

By the way, just in case this helps someone besides me (and since I
wasn't able to find a complete answer to this
question on the list archives -- feel free to chastise me off-list if
you think this was OT).. I finally got my reverse
proxy running perfectly with Seaside and thought I'd put my proxy
settings out for anyone else that happens
to want to do this now or in the future.. Keep in mind that these
settings are for use with Apache2 (not 1.x)
and would need work to be used on an older Apache server..  Hopefully
someone will find this of interest..

############################################################
# Setup the Seaside Reverse Proxy
# derived from the following sites:
#    http://www.wlug.org.nz/ApacheReverseProxy
#    http://www.apacheweek.com/features/reverseproxies
############################################################
ProxyRequests                   off
ProxyPass                       /seaside        
http://localhost:8008/seaside/go/myapp
ProxyHTMLURLMap                 http://www.yourdomain.com/seaside /seaside

<Location /seaside>
        ProxyPassReverse        http://localhost:8008/seaside/go/myapp/
        SetOutputFilter         proxy-html
        ProxyHTMLURLMap         /seaside/go/            /seaside/
        ProxyHTMLURLMap         /seaside/go/myapp/    /seaside/
        RequestHeader           unset Accept-Encoding
</Location>

#ProxyHTMLLogVerbose On
#       LogLevel Debug

So, with the above settings, if you visit
http://www.yourdomain.com/seaside, you'll get a mapping
from your Apache webserver over to
http://localhost:8008/seaside/go/myapp and all pages will
get their internal links rewritten to look something like :

 http://www.yourdomain.com/seaside/myapp?4&_k=VrunGRvS&_s=SOPzHyEkmNFVrnJp

Now, obviously if you wanted to have multiple seaside apps running,
you'd have to tailor this a bit.

Hope this helps... :-)

-- Rick


_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Rick Flower wrote: Thanks Rick, promises to be very helpful in the future for me.
Are there any modules that need to be loaded as well? I try to keep them
to the bare minimum.
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Brad Fuller wrote:
> Thanks Rick, promises to be very helpful in the future for me.
> Are there any modules that need to be loaded as well? I try to keep them
> to the bare minimum.
>  
Here's my section from higher up in my apache2 httpd.conf file :

LoadModule headers_module       modules/mod_headers.so
LoadModule proxy_module         modules/mod_proxy.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_ftp_module     modules/mod_proxy_ftp.so
LoadModule proxy_http_module    modules/mod_proxy_http.so
LoadFile    /usr/lib/libxml2.so
LoadModule proxy_html_module    modules/mod_proxy_html.so
LoadModule rewrite_module       modules/mod_rewrite.so
LoadModule php4_module          modules/libphp4.so

I *think* that's about all I added for the most part..

-- Rick


_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> So, with the above settings, if you visit
> http://www.yourdomain.com/seaside, you'll get a mapping
> from your Apache webserver over to
> http://localhost:8008/seaside/go/myapp and all pages will
> get their internal links rewritten to look something like :

Interesting. Why do you use Apache to rewrite all the links inside the
HTML and not let Seaside produce the actual URLs right from the
beginning?

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Lukas Renggli wrote:
> Interesting. Why do you use Apache to rewrite all the links inside the
> HTML and not let Seaside produce the actual URLs right from the
> beginning?
>
>  
I guess after reading through the various old posts on the Seaside list
I was/am under the
impression that Seaside needs to use one of the built in webservers that
are provided by
either Squeak or VW... If I can decouple Seaside and have it somehow
talk to Apache
directly, I'm all for that, but am not sure if it's possible or how to
do it..

Also, when I re-configure my Seaside application to change the Base Path
to something other
than /seaside/go/myapp, it always jumps right back to that value and
never seems to interested
in taking something else, so I've given up on fiddling with it..   Just
keep in mind that I'm fairly
new to Seaside/Smalltalk and am likely to be doing something that may
not make much sense
to someone else more familiar with this environment.  Please enlighten
me if I'm barking down
the wrong tree...

-- Rick

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> either Squeak or VW... If I can decouple Seaside and have it somehow
> talk to Apache
> directly, I'm all for that, but am not sure if it's possible or how to
> do it..

There is WAModList, but I don't know if it has ever been used.

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside