What's the (technical) purpose of adding t/seaside/ to the path
(was: Re: [Seaside] how to remove '/seaside/someApp')
Ching de la Serna
ching.dls at gmail.com
Sun Jul 22 00:50:36 UTC 2007
I suppose this might depend on the router that you have. On my router, I
only set port forwarding to redirect port 80 to my proxy server. There are
firewall settings which I don't think is relevant to the problem at hand. I
do not see anywhere I can append '/seaside/myApp' so that my proxy will do
the right re-direction. A problem might arise when I have another
application that uses the same router and backend servers. Would I be able
to do stuff on the router side to get the same results?
On 7/20/07, Stephan Eggermont <stephan at stack.nl> wrote:
> On Fri, Jul 20, 2007 at 11:09:50AM +0200,
> seaside-request at lists.squeakfoundation.org wrote:
> > From: "Philippe Marschall" <philippe.marschall at gmail.com>
> > 2007/7/19, Ching de la Serna <ching.dls at gmail.com>:
> > > Hi,
> > >
> > > I have a little problem. How do I remove '/seaside/someApp' such that
> > > could have: 'http://someDomain.com/' instead of '
> > > http://someDomain.com/seaside/someApp'. Help anyone?
> > The short answer is you can't. The long answer is if you run behind
> > Apache 2 (which is a good idea) you can use mod_rewrite to hide it.
> If you're behind a router/firewall you can hide it there so you only
> have the /seaside/someApp internally.
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Seaside