From a3d4edca7dbb21cdcb9833b06899f2d5062df516 Mon Sep 17 00:00:00 2001
From: Jean-Paul Calderone <exarkun@twistedmatrix.com>
Date: Tue, 15 May 2018 10:10:21 -0400
Subject: [PATCH] retrieve server version and info

---
 docs/proposed/http-storage-node-protocol.rst | 23 ++++++++++++++++++++
 1 file changed, 23 insertions(+)

diff --git a/docs/proposed/http-storage-node-protocol.rst b/docs/proposed/http-storage-node-protocol.rst
index 87d383cfd..c524d31bd 100644
--- a/docs/proposed/http-storage-node-protocol.rst
+++ b/docs/proposed/http-storage-node-protocol.rst
@@ -95,6 +95,29 @@ Client node implementations could cache a successful protocol upgrade.
 This would avoid the double connection on subsequent startups.
 This is left as a decision for the implementation, though.
 
+Server Details
+--------------
+
+``GET /v1/version``
+
+Retrieve information about the version of the storage server.
+Information is returned as an encoded mapping.
+For example::
+
+  { "http://allmydata.org/tahoe/protocols/storage/v1" :
+    { "maximum-immutable-share-size": 1234,
+      "maximum-mutable-share-size": 1235,
+      "available-space": 123456,
+      "tolerates-immutable-read-overrun": true,
+      "delete-mutable-shares-with-zero-length-writev": true,
+      "fills-holes-with-zero-bytes": true,
+      "prevents-read-past-end-of-share-data": true,
+      "http-protocol-available": true
+      },
+    "application-version": "1.13.0"
+    }
+
+
 Reading
 -------