SOAP: how to demand <change>?

[ljm]

I'm wondering what to do to guarantee a <change token="xxx"> in the <context> element of a SOAP response? I particularly want the change id/token in relation to a <ModifyBlahResponse>

Currently, my SOAP client is issuing requests using:
<context> <nonotify/><noqualify/></context>
which seems to mostly work fine. Except for one server recently encountered where the (successful) server response contained a completely empty <context> element. I don't have access to the particular server so it's bit tricky to experiment with.

So: what's the right/best way to issue a request that will guarantee a <change token='xxx'> in the response?

[ljm]

As far as I can tell from reading soap.txt, the server should provide a <change> element in it's response. Otherwise it's a server bug.

This issue is proving to be an ongoing source of bugs for zindus users. So if my understanding about this is wrong, it would be great is someone could clarify.

ie. if <change> is optional in the server response and there's something a client can/should do to force it, it would be great to know that.

[luh3417]

Originally Posted by ljm

As far as I can tell from reading soap.txt, the server should provide a <change> element in it's response. Otherwise it's a server bug.

This issue is proving to be an ongoing source of bugs for zindus users. So if my understanding about this is wrong, it would be great is someone could clarify.

ie. if <change> is optional in the server response and there's something a client can/should do to force it, it would be great to know that.

I am here because I got this error out notice. I have reset and I still get it. This bug seems very old. Is there a fix?
Thanks

You have encountered a known Zimbra bug: SOAP: how to demand <change>?

Suggest 'Reset' followed by 'Sync Now'.