Thanks for the bug report. I think this is fixed with server 2.3.x ( Server 2.3.1 beta/Client 2.3.0 beta )