require a valid uuid at the end of an annex+http url

This commit is contained in:
Joey Hess 2024-07-23 12:30:27 -04:00
parent 75b1d50b99
commit 2aa9154b1f
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 32 additions and 12 deletions

View file

@ -9,8 +9,10 @@ connection (mostly). This is a translation of that protocol to HTTP.
To indicate that an url uses this protocol, use
`annex+http` or `annex+https` as the url scheme. Such an url uses
port 9417 by default, although another port can be specified. For example,
`annex+http://example.com/` or `annex+http://example.com:80/`
port 9417 by default, although another port can be specified.
The last part of the path of such an url is always the repository uuid.
For example, `annex+http://example.com/git-annex/$uuid` or
`annex+http://example.com:80/git-annex/$uuid`
## base64 encoding of keys, uuids, and filenames

View file

@ -17,8 +17,8 @@ API.
Typically a remote will have `remote.name.url` set to a http url
as usual, and `remote.name.annexUrl` set to an annex+http url such as
`annex+http://example.com/`. The annex+http url is served by this
server, and uses port 9417 by default.
`annex+http://example.com/git-annex/$uuid`. The annex+http url is
served by this server, and uses port 9417 by default.
As well as serving the git-annex HTTP API, this server provides a
convenient way to download the content of any key, by using the path