[Seaside] seaside with mod proxy: mapping urls to applications

Colin Putney seaside@lists.squeakfoundation.org
Sat, 30 Nov 2002 10:54:03 -0800


I haven't been able to solve this problem either. (Though I'm using 
Seaside 1). At some point we'll need to teach seaside to distinguish 
between the urls through which it is reached, and the urls it generates 
in the HTML. That will give us a lot more flexibility to integrate 
Seaside into more complex systems for load-balancing, proxying etc.



On Friday, November 29, 2002, at 08:15  PM, Derek Brans wrote:

> How do you map urls to WAApplications with mod proxy?
>
> ProxyPass  	/seaside	http://127.0.0.1:8000/seaside
> ProxyPassReverse  	/seaside	http://127.0.0.1:8000/seaside
>
> That works, but if I want to map /calendar to a seaside application:
>
> ProxyPass  	/calendar	http://127.0.0.1:8000/seaside/sandcaster
> ProxyPassReverse  	/calendar	http://127.0.0.1:8000/seaside/sandcaster
>
> doesn't work...
> You would expect it to load 
> www.mydomain.com/calendar/4;123412094209374 (sample session id)
> but instead, apache is looking for 
> www.mydomain.com/seaside/sandcaster/4;123412094209374, which it can't 
> find.