From 5e90f3d3df466e09b388c57a1b193ae4ce7f2eee Mon Sep 17 00:00:00 2001 From: Meta Vens Date: Mon, 19 Oct 2026 18:26:58 +0200 Subject: [PATCH] cultmesh-browser README: redirects, plain endpoints and unallocatable sizes Co-Authored-By: Claude Opus 5.5 --- packages/cultmesh-browser/README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/packages/cultmesh-browser/README.md b/packages/cultmesh-browser/README.md index daefaa77..52410834 100644 --- a/packages/cultmesh-browser/README.md +++ b/packages/cultmesh-browser/README.md @@ -77,7 +77,10 @@ to it before and after route rotation. The endpoint comes from CultMesh and never from content: a manifest carries no URL. No byte is released that failed its chunk or whole-body SHA-256 (WebCrypto, so a secure context in browsers). Only https is accepted, and http only on -loopback. Options: `maxConcurrentChunkRequests` (1 to 32, default 4), `maxBytes` +loopback; a redirect is a `network` failure, and an endpoint spelling on which +.NET `UriBuilder` and WHATWG `URL` would build different request URLs (non-ASCII, +`'` `{` `}` `|` `^` `\` or a space, a stray `%`, an escaped unreserved character) +is `insecure-endpoint`. A size the runtime cannot allocate is `too-large`. Options: `maxConcurrentChunkRequests` (1 to 32, default 4), `maxBytes` (default 256 MiB, checked before any request), `signal` (an abort rejects with the signal's own reason). Failures are `CultMeshContentError` with a `code` (`manifest-invalid`, `too-large`, `insecure-endpoint`, `webcrypto-unavailable`,