UNLOCKCONTENT is not a top-level request
proxyRequest was treating UNLOCKCONTENT as a separate request. That made it possible for there to be two different connections to the proxied remote, with LOCKCONTENT being sent to one, and UNLOCKCONTENT to the other one. A protocol error. git-annex testremote now passes against a http proxied remote.
This commit is contained in:
parent
a3dab58be2
commit
0fb86d2916
4 changed files with 16 additions and 33 deletions
|
@ -114,8 +114,10 @@ the client sends:
|
|||
LOCKCONTENT Key
|
||||
|
||||
The server responds with either SUCCESS or FAILURE.
|
||||
The former indicates the content is locked. It will remain
|
||||
locked until the client sends its next message, which must be:
|
||||
The former indicates the content is locked.
|
||||
|
||||
After SUCCESS, the content will remain locked until the
|
||||
client sends its next message, which must be:
|
||||
|
||||
UNLOCKCONTENT Key
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue