Distinguish asset read failures from unknown writes
This commit is contained in:
@@ -43,7 +43,9 @@ missing, conflicting, or unverifiable. Same-name attachments with different
|
||||
bytes are conflicts even when their reported size matches. An existing
|
||||
`SHA256SUMS` must exactly match the complete expected manifest; a subset or
|
||||
different manifest is a conflict. An unreadable attachment is unverifiable,
|
||||
not missing. Unrelated attachments are returned separately and are preserved.
|
||||
not missing. A failed read-only inspection reports `not_attempted`; if this
|
||||
invocation already delivered the page, its outcome retains `partial` progress.
|
||||
Unknown-write outcomes are reserved for unresolved writes. Unrelated attachments are returned separately and are preserved.
|
||||
|
||||
Attachment downloads and same-origin redirects carry authorization only when
|
||||
their scheme, host, and port match the configured Gitea service. Cross-origin
|
||||
|
||||
Reference in New Issue
Block a user