docs/protocol-v2: point readers transport config discussion
We recently added tips for server admins to configure various transports to support v2's GIT_PROTOCOL variable. While the protocol-v2 document is pretty technical and not of interest to most admins, it may be a starting point for them to figure out how to turn on v2. Let's put some pointers from there to the other documentation. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
parent
2834a72d5e
commit
1b421e7a5a
@ -42,7 +42,8 @@ Initial Client Request
|
|||||||
In general a client can request to speak protocol v2 by sending
|
In general a client can request to speak protocol v2 by sending
|
||||||
`version=2` through the respective side-channel for the transport being
|
`version=2` through the respective side-channel for the transport being
|
||||||
used which inevitably sets `GIT_PROTOCOL`. More information can be
|
used which inevitably sets `GIT_PROTOCOL`. More information can be
|
||||||
found in `pack-protocol.txt` and `http-protocol.txt`. In all cases the
|
found in `pack-protocol.txt` and `http-protocol.txt`, as well as the
|
||||||
|
`GIT_PROTOCOL` definition in `git.txt`. In all cases the
|
||||||
response from the server is the capability advertisement.
|
response from the server is the capability advertisement.
|
||||||
|
|
||||||
Git Transport
|
Git Transport
|
||||||
@ -58,6 +59,8 @@ SSH and File Transport
|
|||||||
|
|
||||||
When using either the ssh:// or file:// transport, the GIT_PROTOCOL
|
When using either the ssh:// or file:// transport, the GIT_PROTOCOL
|
||||||
environment variable must be set explicitly to include "version=2".
|
environment variable must be set explicitly to include "version=2".
|
||||||
|
The server may need to be configured to allow this environment variable
|
||||||
|
to pass.
|
||||||
|
|
||||||
HTTP Transport
|
HTTP Transport
|
||||||
~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~
|
||||||
@ -81,6 +84,9 @@ A v2 server would reply:
|
|||||||
Subsequent requests are then made directly to the service
|
Subsequent requests are then made directly to the service
|
||||||
`$GIT_URL/git-upload-pack`. (This works the same for git-receive-pack).
|
`$GIT_URL/git-upload-pack`. (This works the same for git-receive-pack).
|
||||||
|
|
||||||
|
The server may need to be configured to pass this header's contents via
|
||||||
|
the `GIT_PROTOCOL` variable. See the discussion in `git-http-backend.txt`.
|
||||||
|
|
||||||
Capability Advertisement
|
Capability Advertisement
|
||||||
------------------------
|
------------------------
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user