Excellent question! I tested your hypothesis by changing from an address to a bogus name (ptc-dantoo) and then adding that name only to the host file on the system hosting the Resin proxy servlet. On a third machine on the network, I connected to the proxy again. The link returned by the host was:
http://ptc-dantoo/test2.html which failed. So it appears that Resin's proxy servlet is inserting the host name or IP address provided in the configuration. <snip> <init host='ptc-dantoo:80'/> </snip> Thoughts? Dan > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:resin-interest- > [EMAIL PROTECTED] On Behalf Of Daniel Lopez > > Which kind of logic is "forwarding" the back-end server's IP to the client > browser? Is your application building the URLs using getLocalAddr() or > getServerName()? Otherwise, if you construct your URLs as relative paths, > there is no way the browser should know about the back-end server. > > Salute! > D. > > > > thanks! > > I've implemented this... BUT > > When a machine connects to the external (NAT) address of my RESIN web > > server and it proxies to an internal IP address, the internal IP > > address is the forwarded back to the client. As an example: > > resin.conf: > ... > > When I connect to my host, internally or externally, the client tries to > > make a direct conection to the 192.168.123.16 address. Bummer. > > > > Internally it works fine, but kind of defeats the purpose of having a > > proxy, no? Is there any magic I can use to make it continue to use a > > relative URL? > > _______________________________________________ resin-interest mailing list [email protected] http://maillist.caucho.com/mailman/listinfo/resin-interest
