From f940eb1ec34a1859a4134eb178fe2fa81fb357d6 Mon Sep 17 00:00:00 2001 From: Roberto Polli Date: Wed, 28 Aug 2024 13:13:01 +0200 Subject: [PATCH] Fix: #2877. Reference RFC9111 --- draft-ietf-httpbis-resumable-upload.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/draft-ietf-httpbis-resumable-upload.md b/draft-ietf-httpbis-resumable-upload.md index 27598c08b..30c7a3397 100644 --- a/draft-ietf-httpbis-resumable-upload.md +++ b/draft-ietf-httpbis-resumable-upload.md @@ -45,6 +45,7 @@ author: normative: HTTP: RFC9110 + CACHING: RFC9111 RFC9112: display: HTTP/1.1 RFC5789: @@ -315,7 +316,7 @@ The offset MUST be accepted by a subsequent append ({{upload-appending}}). Due t The client MUST NOT start more than one append ({{upload-appending}}) based on the resumption offset from a single offset retrieving request. -In order to prevent HTTP caching, the response SHOULD include a `Cache-Control` header field with the value `no-store`. +In order to prevent HTTP caching ({{CACHING}}), the response SHOULD include a `Cache-Control` header field with the value `no-store`. If the server does not consider the upload resource to be active, it MUST respond with a `404 (Not Found)` status code.