Clarify the Range header on a chunked push response

This clarifies the Range header response should be the range of the entire blob and not the last received chunk.

Signed-off-by: Brandon Mitchell <[email protected]>

Author: sudo-bmitch

conformance/02_push_test.go

@@ -237,6 +237,7 @@ var test02Push = func() {
 				Expect(err).To(BeNil())
 				location := resp.Header().Get("Location")
 				Expect(resp.StatusCode()).To(Equal(http.StatusAccepted))
+				Expect(resp.Header().Get("Range")).To(Equal(fmt.Sprintf("0-%d", len(testBlobB)-1)))
 				Expect(location).ToNot(BeEmpty())
 				lastResponse = resp
 			})

spec.md

@@ -377,7 +377,7 @@ Range: 0-<end-of-range>
 
 Each consecutive chunk upload SHOULD use the `<location>` provided in the response to the previous chunk upload.
 
-The `<end-of-range>` value is the position of the last uploaded byte.
+The `<end-of-range>` value is the position of the last uploaded byte of the blob, matching the end value of the `Content-Range` in the request.
 
 Chunks MUST be uploaded in order, with the first byte of a chunk being the last chunk's `<end-of-range>` plus one.
 If a chunk is uploaded out of order, the registry MUST respond with a `416 Requested Range Not Satisfiable` code.