Skip to content

Commit 09c5671

Browse files
authored
Update draft-ietf-httpapi-idempotency-key-header.md
Changed a language a bit to address comments wrt returning error codes, once the request is processed by the resource server. (This is work in progress and the next commit would clarify a bit around server side idempotency key to prevent any sort of security leaks
1 parent cdcc9ea commit 09c5671

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

draft-ietf-httpapi-idempotency-key-header.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -129,15 +129,15 @@ For each request, server SHOULD
129129

130130
## Idempotency Enforcement Scenarios
131131

132-
* First time request (idempotency key or fingerprint has not been seen)
132+
* First time request (idempotency key and fingerprint has not been seen)
133133

134134
The resource server SHOULD process the request normally and respond with an appropriate response and status code.
135135

136-
* Duplicate request (idempotency key or fingerprint has been seen)
136+
* Duplicate request (idempotency key and fingerprint has been seen)
137137

138138
Retry
139139

140-
The request was retried after the original request completed. The resource server MUST respond with the result of the previously completed operation, success or an error.
140+
The request was retried after the original request completed. The resource server SHOULD respond with the result of the previously completed operation, success or an error. See Error Scenarios for details on errors.
141141

142142
Concurrent Request
143143

@@ -164,8 +164,9 @@ If the request is retried, while the original request is still being processed,
164164
Link: <https://developer.example.com/idempotency>;
165165
rel="describedby"; type="text/html"
166166

167-
For other errors, the resource MUST return the appropriate status code and error message.
167+
Error scenarios above describe the processing status of an idempotent request by the resource server. Clients MUST correct the requests before performing a retry operation, or the the resource server MUST fail the request and return one of the above errors.
168168

169+
For other 4xx/5xx errors, such as 500,502,504,429, 401, 403, the client SHOULD act appropriately by following the documementation provided by the resource server.
169170

170171

171172
# IANA Considerations

0 commit comments

Comments
 (0)