summaryrefslogtreecommitdiff
path: root/core/api-sync.rst
diff options
context:
space:
mode:
Diffstat (limited to 'core/api-sync.rst')
-rw-r--r--core/api-sync.rst12
1 files changed, 6 insertions, 6 deletions
diff --git a/core/api-sync.rst b/core/api-sync.rst
index 69d6f002..fae93eb1 100644
--- a/core/api-sync.rst
+++ b/core/api-sync.rst
@@ -196,19 +196,19 @@ Receiving Terms of Service
.. http:post:: /backups/${ACCOUNT-KEY}
Upload a new version of the account's database, or download the
- latest version. The request SHOULD include the "Expect: 100 Continue"
- header. The client then SHOULD wait for "100 Continue" before proceeding
+ latest version. The request SHOULD include the ``Expect: 100 Continue``
+ header. The client then SHOULD wait for ``100 Continue`` before proceeding
with the upload, regardless of the size of the upload.
**Request**
- The request must include a "If-Match" header indicating the latest
+ The request must include a ``If-Match`` header indicating the latest
version of the account's database known to the client. If the server
- knows a more recent version, it will respond with a "409 conflict"
+ knows a more recent version, it will respond with a ``409 conflict``
and return the server's version in the response. The client must
then merge the two versions before retrying the upload. Note that
- a "409 Conflict" response will typically be given before the upload,
- (instead of "100 continue"), but may also be given after the upload,
+ a ``409 Conflict`` response will typically be given before the upload,
+ (instead of ``100 continue``), but may also be given after the upload,
for example due to concurrent activities from other accounts on the
same account!