atmResource.getRequest().getRemoteAddr() always returns "0.0.0.0" on WildFly 14 with websockets

[ronnybremer]

For audit reasons I need to know the IP address of the invoking party of our web socket services. According to a post from a couple of years ago, you can get the underlying request through atmResource.getRequest() and use getRemoteAddr() from there. However, running behind Wildfly 14 and using web sockets I always get back "0.0.0.0". There was a similar issue in request #757 behind Tomcat, but that one is also years old.

In a rest endpoint in the same WAR I can successfully get the remote IP address.

Any idea?

Thanks,
Ron

[jfarcand]

In a rest endpoint in the same WAR I can successfully get the remote IP address.

Have you try with another container to see if that work? Could you share a test case? Thanks

[ronnybremer]

I tried to port the application to another container, not so easy as it turned out. I will try to make a small test case to reproduce the issue. On 25 May 2019, at 00:55, Jeanfrancois Arcand <[email protected]<mailto:[email protected]>> wrote: In a rest endpoint in the same WAR I can successfully get the remote IP address. Have you try with another container to see if that work? Could you share a test case? Thanks — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#2370?email_source=notifications&email_token=AEAZ5YORRLBMHBYKRDGBKJTPXBP3XA5CNFSM4HPP65U2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWGUP2I#issuecomment-495798249>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AEAZ5YOWNLG6SO7EYV7HT4DPXBP3XANCNFSM4HPP65UQ>.