From ab284dc093b5a2d88f5de3618891309bbf5e1b6c Mon Sep 17 00:00:00 2001
From: Marius <marius@transloadit.com>
Date: Thu, 19 Oct 2023 14:42:40 +0200
Subject: [PATCH] Recommend response code for HEAD requests

Clarifies the question from https://github.com/tus/tus-resumable-upload-protocol/issues/192. We don't use `MUST` because technically we allowed all status codes before and don't want to make some server implementations incompatible now.
---
 protocol.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/protocol.md b/protocol.md
index e1a10ab..8a0fdc9 100644
--- a/protocol.md
+++ b/protocol.md
@@ -202,6 +202,9 @@ completed. If the size of the upload is known, the Server MUST include the
 SHOULD return either the `404 Not Found`, `410 Gone` or `403 Forbidden` status
 without the `Upload-Offset` header.
 
+The Server SHOULD acknowledge successful `PATCH` requests with a
+`200 OK` or `204 No Content` status.
+
 The Server MUST prevent the client and/or proxies from caching the response by
 adding the `Cache-Control: no-store` header to the response.