Follow up to r29314 with a documentation correction.
* subversion/libsvn_ra_svn/protocol: The repos capabilities list is on
repos-info, not auth-request.
Found by: glasser
git-svn-id: https://svn.apache.org/repos/asf/subversion/branches/mergeinfo-capability@869417 13f79535-47bb-0310-9956-ffa450edef68
diff --git a/subversion/libsvn_ra_svn/protocol b/subversion/libsvn_ra_svn/protocol
index 52b0d27..115b7d8 100644
--- a/subversion/libsvn_ra_svn/protocol
+++ b/subversion/libsvn_ra_svn/protocol
@@ -119,18 +119,14 @@
an authentication request, which is a command response whose arguments
match the prototype:
- auth-request: ( ( mech:word ... ) realm:string ( cap:word ... ) )
+ auth-request: ( ( mech:word ... ) realm:string )
The mech values give a list of SASL mechanisms supported by the
server. The realm string is similar to an HTTP authentication realm
as defined in [RFC 2617]; it allows the server to indicate which of
-several protection spaces the server wishes to authenticate in. The
-cap values list the repository capabilities (that is, capabilities
-that require both the server and repository to support them before the
-server can claim them as capabilities, e.g., SVN_RA_SVN_CAP_MERGEINFO).
-
-If the mechanism list is empty, then no authentication is required and
-no further action takes place as part of the authentication challenge;
+several protection spaces the server wishes to authenticate in. If
+the mechanism list is empty, then no authentication is required and no
+further action takes place as part of the authentication challenge;
otherwise, the client responds with a tuple matching the prototype:
auth-response: ( mech:word [ token:string ] )
@@ -166,11 +162,15 @@
After a successful authentication exchange, the server sends a command
response whose parameters match the prototype:
- repos-info: ( uuid:string repos-url:string )
+ repos-info: ( uuid:string repos-url:string ( cap:word ... ) )
-uuid gives the universal unique identifier of the repository, and
-repos-url gives the URL of the repository's root directory. The
-client can now begin sending commands from the main command set.
+uuid gives the universal unique identifier of the repository,
+repos-url gives the URL of the repository's root directory, and the
+cap values list the repository capabilities (that is, capabilities
+that require both server and repository support before the server can
+claim them as capabilities, e.g., SVN_RA_SVN_CAP_MERGEINFO).
+
+The client can now begin sending commands from the main command set.
2.1 Capabilities
