Definitely too difficult to communicate using email! Please read the scenario I was framing my response under. As an application that is bought, you do not have control over the environment it will be installed in so firewalls do come to play in my mind. This thing has been beaten to death! I think a Filter was the first thing we suggested anyway but that was shot down hence my framing of the problem domain in what I thought was happening where these other concerns would start coming up.
Happy to hear that you got what you needed Martin! Regards...djsuarez -----Original Message----- From: Dakota Jack [mailto:[EMAIL PROTECTED] Sent: Friday, January 28, 2005 9:49 AM To: Struts Users Mailing List Cc: Martin Wegner Subject: Re: PlugIn and the base URL <snip> On Fri, 28 Jan 2005 08:02:46 -0600, David Suarez <[EMAIL PROTECTED]> wrote: > Just the same, it's > likely not a problem for your server to figure out where the request > came from if that is needed for the protocol (the receiver of the > initial message). It's the callback that you have a problem with and it > sounds like it's for a reason... It doesn't make sense to assume that > the web service installed on the client inside some network will be > reachable from the external network. If this is what you're doing, > configuration (having the client app user set the URL) is the only way > to set it up because they (the client) will likely need to open up some > incoming requests that they normally would not allow through their > firewalls anyway. Not to mention whatever you grab would be the > "internal" ip addresses. If your server grabs the ip from the request, > it is likely to a proxy somewhere and not to your app. </snip> This would seem to make sense, I guess, David S., but it does not. The ip address you want is the one that a foreign user should use to get to you and if you send a request, as I suggested, via a mini-browser in your PlugIn, the TCP/IP HTTP protocols will send to the recipient the IP address needed to reach your machine. Then, that machine can send back to you what that is. I know this works because I do it all the time. You can determine the same thing by sending the message to another machine on another port in the same intranet. Jack -- ------------------------------ "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~ "You can't wake a person who is pretending to be asleep." ~Native Proverb~ "Each man is good in His sight. It is not necessary for eagles to be crows." ~Hunkesni (Sitting Bull), Hunkpapa Sioux~ ----------------------------------------------- "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
