Henning P. Schmiedehausen wrote:
In case you use Tomcat with a HTTP connector behind firewall/NAT there is a solution."Chris K Chew" <[EMAIL PROTECTED]> writes: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.Only if you don't NAT / rewrite addresses. If you have this scenario: Internet ----- Firewall ------ server.foo.org visible as xxx.foo.org and you request http://xxx.foo.org/app/servlet/app/ then turbine will get "server.foo.org" in the HTTP Request, because that's what the server knows about. So all the links in the page will contain http://server.foo.org/app/servlet/app/ which does not work. There is currently no easy way around this. I might consider hand-stuffing the ServerData object from the properties for this scenario. Ping me for it, once we have a 2.2 release. Regards Henning
You can configure Tomcat's HTTP Connector so that all requests channeled thru this connector will let Turbine think that it has the name of your public website. As consequence all DynamicURI methods will deliver the correct links of your public site.
For more info see http://jakarta.apache.org/tomcat/tomcat-4.0-doc/proxy-howto.html
(Especially step 4).
Success,
Bart
*************************************************************************
The information contained in this communication is confidential and is
intended solely for the use of the individual or entity to whom it is
addressed.You should not copy, disclose or distribute this communication without the authority of iBanx bv. iBanx bv is neither liable for the proper and complete transmission of the information has been maintained
nor that the communication is free of viruses, interceptions or interference.
If you are not the intended recipient of this communication please return
the communication to the sender and delete and destroy all copies.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
