This project has moved. For the latest updates, please go here.

[en] Client address (solved)

Topics: Technical Support
Oct 18, 2013 at 5:26 AM
Edited Oct 18, 2013 at 5:26 AM
1) From my tests (Win7 x64, client and server on same machine) client address is available (in ClientLoggedOn and authentication request) only for TcpDuplexXProtocolSetup and not for TcpCustomXProtocolSetup. Is this normal behavior?
2) Revision 36765: then client address is not available - NullReferenceException in ZyanDispatcher.cs, Logon method, line 648 because GetCallingClientIPAddress() returning null.
Oct 18, 2013 at 7:05 AM
Edited Oct 18, 2013 at 7:09 AM
Terribly sorry about the NullReferenceException!
Looks like I haven't executed the integration tests before my last commit.

Missing ClientAddress property in TcpCustom protocol is not by design.
Seems like most people use TcpDuplex channel, so it just was unnoticed until now.
I've added the required code to all TCP/HTTP protocol setup classes.
Please download the latest source code from SVN repository.

Thanks a lot for reporting these issues!

UPD. Work item.
Marked as answer by zii_dmg on 10/18/2013 at 2:35 AM