correct AUTH-SUCCESS and AUTH-FAILURE

It's AUTH_SUCCESS internally in git-annex, but the line based
serialization uses AUTH-SUCCESS.

diff --git a/doc/design/p2p_protocol.mdwn b/doc/design/p2p_protocol.mdwn
index 7d631789d7443c51a11ded2dcfe37bbb544a1626..90b2352df619e29f75d34f1f5dd14d9e45021147 100644 (file)
--- a/doc/design/p2p_protocol.mdwn
+++ b/doc/design/p2p_protocol.mdwn
@@ -40,7 +40,7 @@ The server responds with either its own UUID when authentication
 is successful. Or, it can fail the authentication, and close the
 connection.
 
-       AUTH_SUCCESS UUID
+       AUTH-SUCCESS UUID
        AUTH_FAILURE
 
 Note that authentication does not guarantee that the client is talking to

diff --git a/doc/design/p2p_protocol_over_http.mdwn b/doc/design/p2p_protocol_over_http.mdwn
index 913d530aefd32850df5f274141efd89e1ae07ca3..4c67f0d0bffd8c6ae198bf3d17cbb7ba0b8a3bdb 100644 (file)
--- a/doc/design/p2p_protocol_over_http.mdwn
+++ b/doc/design/p2p_protocol_over_http.mdwn
@@ -35,7 +35,7 @@ For example (eliding the full HTTP responses, only showing the data):
     > Content-Length: ...
     > 
     > AUTH 79a5a1f4-07e8-11ef-873d-97f93ca91925 
-    < AUTH_SUCCESS ecf6d4ca-07e8-11ef-8990-9b8c1f696bf6
+    < AUTH-SUCCESS ecf6d4ca-07e8-11ef-8990-9b8c1f696bf6
 
     > POST /git-annex HTTP/1.0
     > Content-Type: x-git-annex-p2p
@@ -80,7 +80,7 @@ correspond to each action in the P2P protocol.
 Something like this:
 
     > GET /git-annex/v1/AUTH?clientuuid=79a5a1f4-07e8-11ef-873d-97f93ca91925 HTTP/1.0
-    < AUTH_SUCCESS ecf6d4ca-07e8-11ef-8990-9b8c1f696bf6
+    < AUTH-SUCCESS ecf6d4ca-07e8-11ef-8990-9b8c1f696bf6
 
     > GET /git-annex/v1/CHECKPRESENT?key=SHA1--foo&clientuuid=79a5a1f4-07e8-11ef-873d-97f93ca91925&serveruuid=ecf6d4ca-07e8-11ef-8990-9b8c1f696bf6 HTTP/1.0
     > SUCCESS