Understood. This isn't really an issue with my application, but
could be important for others. It would be up to the proxy to add these
fields. It would be nice if the rpc method had access to all this
information. A hashtable with the incoming headers, as well as the data
contained the Socket returned from accept, SSL information if the
connection is SSL (client certificate information, etc)
I am willing to implement it and provide patches if there is some
consensus on how it should be done to so that it is useful to more then
Tino Wildenhain wrote:
>Am Dienstag, den 30.11.2004, 17:42 -0500 schrieb James Russo:
>> I think my original question was not clear. I want the server to be
>>able to obtain the IP address of the client calling the RPC method. I
>>want to be able to get this information from within the RPC method
>>itself. Right now, I don't think it is possible with the current way
>>things are implemented. Other then userpassword (via
>>AuthenticatedXmlRpcHandler, or ContextXmlRpcHandler) no information
>>about the underlying transport is available at the RpcMethod layer.
>When it comes to HTTP - and XMLRPC works on top of HTTP -
>beware of the proxies. The IP you see at server level
>isnt garantied the IP of the client box of the user.
>And it might even be not constant over subsequent
>requests from the same user.
>Best bet if you need some informations about the request
>patch the server so you get all the (cgi) variables like
>REMOTE_HOST, HTTP_X_FORWARDED_FOR, ... whatnot.