[taler-docs] 24/94: mark up ‘200 OK’

[gnunet]

This is an automated email from the git hooks/post-receive script.

ttn pushed a commit to branch master
in repository docs.

commit 66033d5ba6affd02abc2e81138b6a7cdb6184c46
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Wed Apr 7 03:44:25 2021 -0400

    mark up ‘200 OK’
---
 anastasis.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/anastasis.rst b/anastasis.rst
index cabf1fb..41ff3be 100644
--- a/anastasis.rst
+++ b/anastasis.rst
@@ -524,7 +524,7 @@ In the following, UUID is always defined and used according 
to `RFC 4122`_.
   If the client specified a version number in the header of the request, the 
server must return that version. If the client
   did not specify a version in the request, the server returns latest version 
of the EncryptedRecoveryDocument_.
 
-  *Etag*: Set by the server to the Base32-encoded SHA512 hash of the body. 
Used for caching and to prevent redundancies. The server MUST send the Etag if 
the status code is 200 OK.
+  *Etag*: Set by the server to the Base32-encoded SHA512 hash of the body. 
Used for caching and to prevent redundancies. The server MUST send the Etag if 
the status code is ``200 OK``.
 
   *If-None-Match*: If this is not the very first request of the client, this 
contains the Etag-value which the client has received before from the server.
   The client SHOULD send this header with every request (except for the first 
request) to avoid unnecessary downloads.

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.