Document save without history update (dirty=false) produce a conflict when replicated

It's possible using a script and programming right to force saving a document with a specif version and/or without incrementing the history.

In such a case, the "with a specif version and/or without incrementing the history" part is not taken into account by the replication: the document history and version will be incremented naturally on other instances when they receive it.
The version and date are now correct, but this weird input is identified as a conflict.