[taler-docs] branch master updated: delete extra indentation (eight instances)

[gnunet]

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

ttn pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 832e4a4  delete extra indentation (eight instances)
832e4a4 is described below

commit 832e4a4be5ffe65b408f0be1a4b67f126795e6a2
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Sat Nov 28 00:24:29 2020 -0500

    delete extra indentation (eight instances)
---
 anastasis.rst | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/anastasis.rst b/anastasis.rst
index 29f395f..c03620f 100644
--- a/anastasis.rst
+++ b/anastasis.rst
@@ -534,16 +534,16 @@ In the following, UUID is always defined and used 
according to `RFC 4122`_.
      case.
 
   *If-Match*: Unless the client expects to upload the first encrypted recovery 
document to this account, the client
-    SHOULD provide an Etag matching the latest version already known to the 
server.  If this
-    header is present, the server MUST refuse the upload if the latest known 
version prior to
-    this upload does not match the given Etag.
+  SHOULD provide an Etag matching the latest version already known to the 
server.  If this
+  header is present, the server MUST refuse the upload if the latest known 
version prior to
+  this upload does not match the given Etag.
 
   *If-None-Match*: This header MUST be present and set to the SHA512 hash 
(Etag) of the body by the client.
-    The client SHOULD also set the "Expect: 100-Continue" header and wait for 
"100 continue"
-    before uploading the body.  The server MUST
-    use the Etag to check whether it already knows the encrypted recovery 
document that is about to be uploaded.
-    The server MUST refuse the upload with a "304" status code if the Etag 
matches
-    the latest version already known to the server.
+  The client SHOULD also set the "Expect: 100-Continue" header and wait for 
"100 continue"
+  before uploading the body.  The server MUST
+  use the Etag to check whether it already knows the encrypted recovery 
document that is about to be uploaded.
+  The server MUST refuse the upload with a "304" status code if the Etag 
matches
+  the latest version already known to the server.
 
   *Anastasis-Policy-Signature*: The client must provide Base-32 encoded EdDSA 
signature over hash of body with $ACCOUNT_PRIV, affirming desire to upload an 
encrypted recovery document.
 

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