Client Submits an Invalid collblob

Topic Last Modified: 2006-06-12

The collblob held by the client for a collection can become invalid under certain circumstances. A scenario under which the collblob held by a client can become invalid is when the collection is deleted and re-created with the same name as before on the server. In this instance, the collections, as known by the client and server, are different although the URL is the same. Under these circumstances, when the client requests an updated manifest by passing its previous collblob, the server detects that the collections are, in fact, different and returns an error 475 Invalid collblob.

SEARCH /exchange/user0/inbox HTTP/1.1
Host: example.com
Content-type: text/xml
Content-length: {insert length here}

<?xml version="1.0"?>
<D:searchrequest xmlns:D="DAV:"
    xmlns:R="https://schemas.microsoft.com/repl/"
    xmlns:M="urn:schemas:mail:">
    <R:repl>
    <R:collblob>clientopaquedata</R:collblob>
    </R:repl>
    <D:sql>SELECT 'urn:schemas:mail:Size', 'urn:schemas:mail:Importance',
           'https://schemas.microsoft.com/repl/resourcetag'
           FROM SCOPE ('SHALLOW TRAVERSAL OF "/exchange/user0/inbox"')
    </D:sql>
</D:searchrequest>

HTTP/1.1 475 Invalid collblob