From ab9fa3b982caf4ab09929969ae84c124b2c4c772 Mon Sep 17 00:00:00 2001
From: Zdenek Nemec <zdenek@me.com>
Date: Thu, 11 Jul 2019 10:04:49 +0200
Subject: [PATCH] Use retry after instead of pingAfter

---
 rest-api-guidelines/execution/asynchronous-tasks.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/rest-api-guidelines/execution/asynchronous-tasks.md b/rest-api-guidelines/execution/asynchronous-tasks.md
index 7289831..8df4f8a 100644
--- a/rest-api-guidelines/execution/asynchronous-tasks.md
+++ b/rest-api-guidelines/execution/asynchronous-tasks.md
@@ -37,13 +37,14 @@ In the case of callback, the API and its client MUST agree on what HTTP method a
 
     HTTP/1.1 202 Accepted
     Content-Type: application/hal+json
+    Retry-After: 60
 
     {
       "_links": {
         "self": { "href": "/feeds/tasks/1" }
       },
       "message": "Your task to generate feed has been accepted. Try query for result after 60 seconds.",
-      "pingAfter": 60
+      "retryAfter": 60
     }
     ```
 
@@ -55,13 +56,14 @@ In the case of callback, the API and its client MUST agree on what HTTP method a
 
     HTTP/1.1 200 Ok
     Content-Type: application/hal+json
+    Retry-After: 30
 
     {
       "_links": {
         "self": { "href": "/feeds/tasks/1" }
       },
       "message": "Your feed is being generated. Try query for result after 30 seconds.",
-      "pingAfter": 30
+      "retryAfter": 30
     }
     ```