My experience is that Turbine will pick up the firewall's public ip address/port and not the private ip/port.
This because o.a.t.util.DynamicURI eventually uses the ServerData object, which is populated by TurbineRunDataService.getRunData() for each request, according to the request. And the request http headers will contain the ip, hostname/alias, and port of the firewall, because that is where the public client thinks the http server is. As far as my experience goes, a packet-forwarding firewall does not change the http headers, but only the tcp/ip headers. In short, your setup should work fine behind the firewall with no changes to your application, that is, mine does anyway. Chris > -----Original Message----- > From: Prometeo Sandino Roman Corral [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, December 03, 2002 11:24 AM > To: Turbine-User List (E-mail) > Subject: URL resolving question > > > Hello: > I would like to know how Turbine gets the "abolute Path" when > resolving an > specified '$link'? > Specifically if I has my turbine aplication on a "hidden" server (with > private IP) and a firewall receiving all the requests > ( and/or distribuing the charges ).**** > > I suppose that the TemplateLink would resolve a path to a link, by taking > the homologated firewall's IP. > > Does it happen like this? and how it does it? > > This could be a non-turbine question, but thanks in advance! > _____________________________ > Sandino. > > > > **** For instance, if I had: > $link.setPage("index.wm").addPathInfo("hello","world") > This would return: > http://148.273.190.43/Turbine/template/index.wm/hello/world, > > Where "http://148.273.190.43"; would be the firewall's IP. > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
