RavenDB-1555 Even if the appropriate source replication document does not exist we have to add to the response the server id in order to be able to properly apply a replication strategy's filtering option where we prevent replication back to source
RavenDB-1555 Fixing the case that in master-master replication when the second one never replicated he also never updated the last replicated etag, what in turns caused performance issues if there was millions of docs because the second server had to filter out all docs all the time.