Well, in mod_perl 1.x you can always just call Apache->request() to get the current request object. Using the remote IP is usually a bad idea though. You can't expect it to be unique (proxies) and you can't expect the same client to always come in with the same IP (proxies again). | [reply] [d/l] |
BINGO. Worked like a charm testing locally, will test again tomorrow in the dev environment.
In this particular case, the client is going to provide us with a list of possible ip's they'll be connecting to the service with, and we'll be able to associate at least a list of ip's with the user account. agreed, it's not a perfect solution, but it's the one i've been charged with implementing. i'd be delighted, however, to hear an alternative approach i can sell to the powers that be?
Thanks again muchly for the tip, feels good to be unstuck.
c
| [reply] |
| [reply] |
Hello
I don't quite understand why do you need Apache::Request object with SOAP.
1. It is SOAP so it should be free from any data protocol realization
2. The http server should set a branch of environment variables about a current session with remote client.
check this variable $ENV{REMOTE_ADDR} inside your soap handler on the server side.
also check this page to view a list of variables the web server should set
http://hoohoo.ncsa.uiuc.edu/cgi/env.html
| [reply] |