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.rst40
1 files changed, 20 insertions, 20 deletions
diff --git a/core/api-sync.rst b/core/api-sync.rst
index 67d1e214..1e673ed6 100644
--- a/core/api-sync.rst
+++ b/core/api-sync.rst
@@ -94,7 +94,7 @@ itself cannot not enforce these rules.
increment it by the smallest possible amount when uploading an
update.
* In general, the merge operation should be implemented in such a way
- that it deals gracefully with adversarial devices from rouge
+ that it deals gracefully with adversarial devices from rogue
devices connected to the same account.
It is assumed that the synchronization service is only ever accessed
@@ -156,28 +156,28 @@ Receiving Terms of Service
**Response**
- :status 200 OK:
+ :http:statuscode:`200 OK`:
The body contains the current version of the backup
as known to the server.
- :status 204 No content:
+ :http:statuscode:`204 No content`:
This is a fresh account, no previous backup data exists at
the server.
- :status 304 Not modified:
+ :http:statuscode:`304 Not modified`:
The version available at the server is identical to that
specified in the "If-None-Match" header.
- :status 404 Not found:
+ :http:statuscode:`404 Not found`:
The backup service is unaware of a matching account.
- :status 410 Gone:
+ :http:statuscode:`410 Gone`:
The backup service has closed operations. The body will
contain the latest version still available at the server.
The body may be empty if no version is available.
The user should be urged to find another provider.
- :status 429 Too many requests:
+ :http:statuscode:`429 Too many requests`:
This account has exceeded thresholds for the number of
requests. The client should try again later, and may want
to decrease its synchronization frequency.
@@ -186,7 +186,7 @@ Receiving Terms of Service
"200 OK" responses include an HTTP header
"Sync-Signature" with the signature of the
- client from the orginal upload, and an
+ client from the original upload, and an
"Sync-Previous" with the version that was
being updated (unless this is the first revision).
"Sync-Previous" is only given to enable
@@ -249,52 +249,52 @@ Receiving Terms of Service
**Response**
- :status 204 No content:
+ :http:statuscode:`204 No content`:
The transfer was successful, and the server has registered
the new version.
- :status 304 Not modified:
+ :http:statuscode:`304 Not modified`:
The server is already aware of this version of the client.
Returned before 100 continue to avoid upload.
- :status 400 Bad request:
+ :http:statuscode:`400 Bad request`:
Most likely, the uploaded body is too short (less than 32 bytes).
- :status 402 Payment required:
+ :http:statuscode:`402 Payment required`:
The synchronization service requires payment before the
account can continue to be used. The fulfillment URL
should be the /$ACCOUNT-KEY URL, but can be safely ignored
by the client. The contract should be shown to the user
in the canonical dialog, possibly in a fresh tab.
- :status 403 Forbidden:
+ :http:statuscode:`403 Forbidden`:
The signature is invalid or missing (or body does not match).
- :status 409 Conflict:
+ :http:statuscode:`409 Conflict`:
The server has a more recent version than what is given
in "If-Match". The more recent version is returned. The
client should merge the two versions and retry using the
given response's "E-Tag" in the next attempt in "If-Match".
- :status 410 Gone:
+ :http:statuscode:`410 Gone`:
The backup service has closed operations. The body will
contain the latest version still available at the server.
The body may be empty if no version is available.
The user should be urged to find another provider.
- :status 411 Length required:
+ :http:statuscode:`411 Length required`:
The client must specify the "Content-length" header before
attempting upload. While technically optional by the
HTTP specification, the synchronization service may require
the client to provide the length upfront.
- :status 413 Request Entity Too Large:
+ :http:statuscode:`413 Request entity too large`:
The requested upload exceeds the quota for the type of
account. The client should suggest to the user to
migrate to another backup and synchronization service
(like with "410 Gone").
- :status 429 Too many requests:
+ :http:statuscode:`429 Too many requests`:
This account has exceeded daily thresholds for the number of
requests. The client should try again later, and may want
to decrease its synchronization frequency.
@@ -303,7 +303,7 @@ Receiving Terms of Service
Responses with a body include an HTTP header
"Sync-Signature" with the signature of the
- client from the orginal upload, and an
+ client from the original upload, and an
"If-Match" with the version that is
being updated (unless this is the first revision).
@@ -337,7 +337,7 @@ auditors or exchanges.
The client should urge the user to make use of a synchronization
service upon first withdrawal, suggesting one that is free or
accepts payment in the respective currency. If none is available,
-the client should warn the user about the lack of availalable
+the client should warn the user about the lack of available
backups and synchronization and suggest to the user to find a
reasonable service. Once a synchronization service was selected,
the client should urge the user to print the respective key