You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
SDK deploy gate: follow only the redirects the builder follows #97
Follow-up from the PR #96 reviews (round 2). Deferred under the review budget: no third patch round on #96.
The fork's private-SDK deploy gate in scripts/releases/apps-self-host.ts (downloadFromRegistry) should accept exactly what the app builder accepts, no more and no less.
Invariants:
Follow only 301, 302, 303, 307 and 308, the statuses the builder follows (patches/@cloudflare%2Fworker-bundler@0.2.4.patch around :172-194). Treat any other 3xx (300, 304 and the rest) as a non-OK archive response and refuse it, as the builder does at :369-375. (Astra r2 F1-R2: today the gate follows 300/304 with Location, while the builder fails.)
Use the builder's hop limit, or a lower one. (Opus N3: the gate allows 5, the builder 10.)
Off-origin tarball URLs and redirect hops stay refused before any request goes to the other origin (already true).
When it refuses for origin, the message and the self-host README explain the same-origin rule and the Verdaccio public-URL/url_prefix case. (Opus N1)
Activity