[jboss-jira] [JBoss JIRA] Commented: (JBREM-758) Associate remote socket address with the invocation
[ http://jira.jboss.com/jira/browse/JBREM-758?page=comments#action_12388363 ]
Ron Sigal commented on JBREM-758:
---------------------------------
Added CLIENT_ADDRESS (actual value "clientAddress") to
org.jboss.remoting.Remoting, which can be used to retrieve the client side InetAddress
from the InvocationRequest requestPayload. In other words, in the
ServerInvocationHandler, the following code may be used:
InetAddress address = invocation.getRequestPayload().get(Remoting.CLIENT_ADDRESS);
The following transports support this facility: bisocket, sslbisocket, http, https, rmi,
sslrmi, socket, sslsocket.
Unit tests:
For non-ssl transports:
org.jboss.test.remoting.transport.<transport>.clientaddress.<transport>ClientAddressTestCase
e.g.:
org.jboss.test.remoting.transport.socket.clientaddress.SocketClientAddressTestCase
For ssl transports:
org.jboss.test.remoting.transport.<transport>.ssl.clientaddress.<transport>ClientAddressTestCase
e.g.:
org.jboss.test.remoting.transport.socket.ssl.clientaddress.SSLSocketClientAddressTestCase
Waiting for cruisecontrol results.
Still need to work on servlet and sslservlet transports.
Associate remote socket address with the invocation
---------------------------------------------------
Key: JBREM-758
URL: http://jira.jboss.com/jira/browse/JBREM-758
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto)
Reporter: Carlo de Wolf
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
Add remote socket address to the InvocationRequest to allow it to be used for auditing
and filtering.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira