Close endpoint failure types across service and web boundaries
This commit is contained in:
parent
fb94ea2c23
commit
390434bed1
1 changed files with 266 additions and 72 deletions
|
|
@ -51,6 +51,9 @@ non-success decoding policy.
|
|||
Upload requests stream `application/octet-stream`, require
|
||||
`X-Declared-Size`, `X-Content-SHA256`, `X-CSRF-Token`, and an operation id, and
|
||||
return a typed mutation result with the advertised terminal idempotency window.
|
||||
Each delete-batch item contains exactly one typed outcome: a mutation result or
|
||||
a closed dependency-failure code. Producers and consumers reject items with
|
||||
both outcomes or neither outcome.
|
||||
Downloads stream through Nuthatch, reject `Range`, use a safe attachment
|
||||
filename, and set active-content isolation headers. The compiled application
|
||||
page governs its assets with the application content-security policy, and
|
||||
|
|
|
|||
Loading…
Reference in a new issue