[Seaside] Seaside in an Apache virtual server

[Wouter Gazendam]

To test if the 404 is generated by apache or seaside, try to access
your page when the image running seaside is down. This will give you a
clue whether your apache conf is misconfigured or seaside.
We're running a similar config (apache (actually apache-ssl) using mod
proxy to a vw-swazoo with seaside) so I think it should work.

hth,

Wouter

On 8/8/05, radoslav hodnicak <rh at 4096.sk> wrote:
> 
> 
> try to add the seaside part of url. when you're connecting to local image
> you don't do
> 
> http://localhost:3535/ (you will get 'not found' from commanche here)
> 
> but something like
> 
> http://localhost:3535/seaside/counter
> 
> in your example try if
> 
> http://www.domainxxxxx.com/application/seaside/counter
> 
> works
> 
> 
> On Mon, 8 Aug 2005, [iso-8859-1] Sebastián Sastre wrote:
> 
> > Hi all,
> >
> >    What I have?
> >    I'm already have a seaside application runing in a port 3535 and
> > right now it's working with that port opened. I also have a website
> > running with apache2 in domainxxxxx.com showing static content.
> >
> >    What I want?
> >    I want to navigate the seaside application through port 80 in some
> > domain's subdirectory like: www.domainxxxxx.com/application.
> >
> >    What I've done?
> >    My question is if I'm configuring right the apache. I've succesully
> > loaded the mod_proxy (in the apache 2 in a linux Suse 9.1) and done this
> > in the domainxxxxx.com virtual server .conf file:
> >
> > <VirtualHost xx.xx.xx.xx:*>
> >    ServerAdmin webmaster at domainxxxxx.com
> >    ServerName www.domainxxxxx.com
> >    ProxyPass /applicationName http://localhost:3535
> >    ProxyPassReverse /applicationName http://localhost:3535
> >    DocumentRoot /var/www/html/domainxxxxx.com
> >    ...
> > </VirtualHost>
> >
> >    What happend?
> >    The apache2 restarts the service without claims but when I open in a
> > browser http://domainxxxxx.com/application the result is (404) "object
> > not found". When I open http://www.domainxxxxx.com/application I have a
> > Forbidden (403) message.
> >
> >    What I should I do?
> >    Perhaps sombody has a clue of what is going on?
> >
> >    best regards,
> >
> > Sebastián Sastre
> >
> > <mailto:ssastre at seaswork.com.ar> ssastre at seaswork.com.ar
> > Seaswork
> > Special Software Solutions
> > www.seaswork.com.ar <http://www.seaswork.com.ar/>
> >
> > Este mensaje y sus adjuntos son confidenciales y de uso exclusivo para
> > el usuario a quien esta dirigido. Puede contener información amparada
> > por el secreto profesional.
> > Si Ud. no es el destinatario especificado no debe copiar, enviar o
> > utilizar ninguna parte del mismo y/o de sus adjuntos por ningún medio.
> > Las opiniones vertidas son responsabilidad del autor y no son emitidas
> > ni avaladas por SEASWORK a menos que se indique claramente lo contrario
> > y que la identidad y autoridad del autor, para comprometer a nuestra
> > empresa, puedan ser verificados.
> > No se garantiza la integridad de los mensajes enviados por e-mail ni que
> > los mismos sean enviados en termino, o que no contengan errores o virus.
> > El emisor no aceptara responsabilidad por los errores, modificaciones u
> > omisiones que resulten en el mensaje, bajo la hipótesis de que pudo ser
> > modificado.
> >
> >
> 
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/listinfo/seaside
> 
> 
>