correct AUTH-SUCCESS and AUTH-FAILURE

It's AUTH_SUCCESS internally in git-annex, but the line based
serialization uses AUTH-SUCCESS.
This commit is contained in:
Joey Hess 2024-06-10 15:05:41 -04:00
parent 317786d219
commit 7b1548dbfa
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 3 additions and 3 deletions

View file

@ -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 is successful. Or, it can fail the authentication, and close the
connection. connection.
AUTH_SUCCESS UUID AUTH-SUCCESS UUID
AUTH_FAILURE AUTH_FAILURE
Note that authentication does not guarantee that the client is talking to Note that authentication does not guarantee that the client is talking to

View file

@ -35,7 +35,7 @@ For example (eliding the full HTTP responses, only showing the data):
> Content-Length: ... > Content-Length: ...
> >
> AUTH 79a5a1f4-07e8-11ef-873d-97f93ca91925 > 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 > POST /git-annex HTTP/1.0
> Content-Type: x-git-annex-p2p > Content-Type: x-git-annex-p2p
@ -80,7 +80,7 @@ correspond to each action in the P2P protocol.
Something like this: Something like this:
> GET /git-annex/v1/AUTH?clientuuid=79a5a1f4-07e8-11ef-873d-97f93ca91925 HTTP/1.0 > 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 > GET /git-annex/v1/CHECKPRESENT?key=SHA1--foo&clientuuid=79a5a1f4-07e8-11ef-873d-97f93ca91925&serveruuid=ecf6d4ca-07e8-11ef-8990-9b8c1f696bf6 HTTP/1.0
> SUCCESS > SUCCESS