What's the (technical) purpose of adding t/seaside/ to
the path(was: Re: [Seaside] how to remove '/seaside/someApp')
jbjohns at libsource.com
Wed Jul 25 16:23:00 UTC 2007
Again, Seaside is an application that is running under a web server. No
new functionality needs to be added to Seaside, you just need to
configure the web server that serves it to have what ever path you want.
NOTE: I am talking about your *smalltalk* web server, not apache or any
of that kind of stuff. Kommanche, Swazoo, something like that.
Carl Gundel wrote:
> I host my site behind Apache, but not every developer wants or needs
> to use Apache or any other front-end, and there's absolutely no good
> deployment reason to not permit the developer to specify a short
> path. Let the developer determine the requirement one way or the
> other. If adding this capability involves difficult development work,
> well then that's a different matter.
> So while I do use Apache and URL rewriting for my public site, I have
> a need for the short path option with a version of my Seaside based
> software which I plan to distribute.
> -Carl Gundel
> ----- Original Message ----- From: "Ching de la Serna"
> <ching.dls at gmail.com
>> 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
>> 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
>> Seaside mailing list
>> Seaside at lists.squeakfoundation.org
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
More information about the Seaside