From a515ea53d28829716ee904cd2288eb9f92d51ad3 Mon Sep 17 00:00:00 2001 From: Mike Harder Date: Tue, 9 Jul 2024 17:36:56 -0700 Subject: [PATCH] [retry-after] Clarify that header value may not use --- azure/Guidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/azure/Guidelines.md b/azure/Guidelines.md index b248ecea..0beefed6 100644 --- a/azure/Guidelines.md +++ b/azure/Guidelines.md @@ -1073,7 +1073,7 @@ retry-after: (if status not terminal) :no_entry: **DO NOT** include a `result` property in the status monitor for a long-running operation that is not an action-type long-running operation. -:white_check_mark: **DO** include a `retry-after` header in the response if the operation is not complete. The value of this header should be an integer number of seconds that the client should wait before polling the status monitor again. +:white_check_mark: **DO** include a `retry-after` header in the response if the operation is not complete. The value of this header must be a non-negative integer number of seconds that the client should wait before polling the status monitor again. The value of this header must not be an `` string, even though `` is also allowed in the HTTP spec. :white_check_mark: **DO** retain the status monitor resource for some publicly documented period of time (at least 24 hours) after the operation completes.