I don't think there is a way to tell inside of Radiator. You can run
multiple instances of Radiator with each one bound to a different address
using the BindAddress config parameter. This will also give you the
advantage of being able to handle more traffic since you will have multiple
threads
I think %c..
Check the docco
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Timothy G. Wells
Sent: Sunday, August 25, 2002 10:29 PM
To: [EMAIL PROTECTED]
Subject: (RADIATOR) Determine IP address request came to
Greetings,
Has there been anything
: (RADIATOR) Determine IP address request came to
I think %c..
Check the docco
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Timothy G. Wells
Sent: Sunday, August 25, 2002 10:29 PM
To: [EMAIL PROTECTED]
Subject: (RADIATOR) Determine IP address request came
Hello Tim -
As far as I know this is an issue with Perl, although I have copied this
mail to Mike for his comments.
BTW - you can see the IP addresses in a packet dump of the incoming
requests using snoop or tcpdump, but this doesn't really help at the
application level.
regards
Hugh
On
Hi Timothy,
On Mon, 26 Aug 2002 12:15, Hugh Irvine wrote:
Hello Tim -
As far as I know this is an issue with Perl, although I have copied this
mail to Mike for his comments.
Unfortunately, there appears to be no way in perl (or in C for that matter)
for an application to discover after the
