Merge pull request #1193 from tahoe-lafs/3890-mutable-http-api

Mutable storage HTTP API, part 1

Fixes ticket:3890

.circleci/config.yml

@@ -48,8 +48,6 @@ workflows:
           {}
       - "pyinstaller":
           {}
-      - "deprecations":
-          {}
       - "c-locale":
           {}
       # Any locale other than C or UTF-8.
@@ -297,20 +295,6 @@ jobs:
       # aka "Latin 1"
       LANG: "en_US.ISO-8859-1"
 
-
-  deprecations:
-    <<: *DEBIAN
-
-    environment:
-      <<: *UTF_8_ENVIRONMENT
-      # Select the deprecations tox environments.
-      TAHOE_LAFS_TOX_ENVIRONMENT: "deprecations,upcoming-deprecations"
-      # Put the logs somewhere we can report them.
-      TAHOE_LAFS_WARNINGS_LOG: "/tmp/artifacts/deprecation-warnings.log"
-      # The deprecations tox environments don't do coverage measurement.
-      UPLOAD_COVERAGE: ""
-
-
   integration:
     <<: *DEBIAN
 

docs/proposed/http-storage-node-protocol.rst

@@ -743,11 +743,15 @@ For example::
 
   [1, 5]
 
-``GET /v1/mutable/:storage_index?share=:s0&share=:sN&offset=:o1&size=:z0&offset=:oN&size=:zN``
+``GET /v1/mutable/:storage_index/:share_number``
 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 
-Read data from the indicated mutable shares.
-Just like ``GET /v1/mutable/:storage_index``.
+Read data from the indicated mutable shares, just like ``GET /v1/immutable/:storage_index``
+
+The ``Range`` header may be used to request exactly one ``bytes`` range, in which case the response code will be 206 (partial content).
+Interpretation and response behavior is as specified in RFC 7233 § 4.1.
+Multiple ranges in a single request are *not* supported; open-ended ranges are also not supported.
+
 
 ``POST /v1/mutable/:storage_index/:share_number/corrupt``
 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!