docs(http): compare KEYED retry, Retry-After and timeout rules per transport (03-06)
V3, the V2 client and Browser RPC give the same policy names different behaviour. One table in the backend contract doc now states each rule with its code location, and the V2 timeoutMs option says it is not a ceiling. Also notes that an exposed X-Correlation-ID becomes AppFailure.requestId. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
e7f376ac83
commit
84effd0cd8
@@ -106,6 +106,11 @@ export type HttpClientDependencies = Readonly<{
|
||||
payload: unknown,
|
||||
) => MappingResult<unknown>;
|
||||
idempotencyKeyFactory?: () => string;
|
||||
/**
|
||||
* Default total deadline for an operation without its own `timeoutMs`. Not a
|
||||
* ceiling: an operation may set a longer one. V3 treats `REQUEST_TIMEOUT_MS`
|
||||
* as a ceiling instead (03-06).
|
||||
*/
|
||||
timeoutMs?: number;
|
||||
maxRetryAttempts?: number;
|
||||
scheduler?: Scheduler;
|
||||
|
||||
Reference in New Issue
Block a user