fix: browser downloads via the CORS asset front door (5.2.0) - #60
Merged
Conversation
GH Releases redirect lacks ACAO: rewrite interscript-ml release URLs to api.interscript.org/v1/assets (sha256 verification unchanged - the channel is never trusted); fetch loop fails loudly on zero bytes instead of returning an empty artifact. Completes TODO.client-work 13 (proxy live as api-worker 1.3.1).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The registry rewrites release URLs to the worker proxy in-browser; integrity still proven by the sidecar sha256 (channel explicitly untrusted). Zero-byte fetches raise instead of yielding an empty artifact. Completes 13 together with api-worker 1.3.1 (proxy already live).