On Wed, Feb 16, 2005 at 07:14:24PM -0500, Stas Bekman wrote:
Yes, it is (though keep in mind that this is a virtual server running as a jailed process, not a separate machine).
That could be the reason.
But if I open a lynx session and surf over to localhost, my server comes up fine.
I've never said it was wrong. As you know when you assign your machine an IP, it can still internally be accessed by loopback device which is always 127.0.0.1 or ::1 on ipv6 machines.
Well, basically you want to figure out how to make Apache-Test see the same value as Apache. i.e. teach our_remote_addr() to get the same value.
It's Apache::Connection which defines the remote_ip() function that is getting the full ip, as opposed to our_remote_addr() which gets the ip defined by localhost (127.0.0.1).
Since the test is for pnotes, we could change the test. However, I suspect it'd be better to figure out what's causing the difference between the two functions. Is this the right place to file a bug report against Apache::Connection?
There is no problem with Apache::Connection. There is no "problem" at all. As explained above both are correct. For the sake of the test all we want is that they agree. That's why I have asked you to figure out how to match
our_remote_addr() with remote_ip(), since the latter can't be changed.
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
