WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our application needs to be able to store the client address of a client in a database for any auditable action.
When those actions are initiated via an RSocket request, there is no possibility to retrieve the client IP via normal actions.
Of course there are some dirty ways around, like using reflection to expose the connection fields of the RSocket server or the Requester, but this feels like hacking, and reverting the field exposition results in access errors.
(I'm at this moment using the solution in issue #831, which works, but feels hacky)
Can the connection fields or just the headers be exposed in the RSocket and Requester classes instead of keeping them protected?