Dnia 2013-07-06, sob o godzinie 20:33 -0600, Peter Saint-Andre pisze: > > 190221: Send(testClient): <iq xmlns="jabber:client" type="result" > > id="wygwyuoi" /> > > This is wrong behavior by the server -- it's not correct to send an > IQ-result in response to a prior IQ-result: > > > 190221: Recv(testClient): <iq xmlns="jabber:client" > > to="[email protected]/testim.5027 > > <http://[email protected]/testim.5027>" > > from="[email protected]/testim.5027 > > <http://[email protected]/testim.5027>" id="wygwyuoi" > > type="result" /> > > Somehow the server is confused and sends you an error (perhaps because > it didn't expect the client to ack the roster push):
Please submit a bug report at: https://github.com/jabberd2/jabberd2/issues/new > Do note that this business about acking the roster pushes was not > clear in RFC 3921 (the precursor to RFC 6121), so it is possible that > jabberd2 is following the older way of doing things. Correct. jabberd2 implements RFC 3921 + some updates from wip versions of bis, but it wasn't fully updated for RFC 6121 compliance. Please submit bugs when you find them and I will fix them ASAP. -- Tomasz Sterna :(){ :|:&};: Instant Messaging Consultant Open Source Developer http://abadcafe.pl/ http://www.xiaoka.com/portfolio
