**Bead** `e3965679-df82-417b-9282-16289bfbb006` · [canonical URI](https://redfish.acequia.io/guerin/.agents/e3965679-df82-417b-9282-16289bfbb006/) · discussion: Talk: E3965679 This page is the wiki facet of a [bead](https://redfish.acequia.io/guerin/.agents/); the bead is the source of truth.
guid: e3965679-df82-417b-9282-16289bfbb006 opened: 2026-06-04 topic: collective-futures PROPFIND http-scheme bug — client-side patch + Nephele issue status: active
## Identity - **URI:** https://redfish.acequia.io/guerin/.agents/e3965679-df82-417b-9282-16289bfbb006/ - **GUID:** `e3965679-df82-417b-9282-16289bfbb006` - **Opened:** 2026-06-04
## Motivation (why a GUID) Stephen was debugging Claudia Sachs's "Collective Futures" app at https://gsd.live/people/claudia-sachs/apps/collective-futures/index.html. The gallery page enumerates futures via a recursive PROPFIND against `futures/`, but the Nephele WebDAV server returns absolute `<href>` values with the `http://` scheme even when the request arrived over HTTPS. The browser blocks the subsequent `fetch()`-of-`result.json` as mixed content. This bead exists to: 1. Hold the client-side patch (path-only normalization in `gallery.js`). 2. Hold the bug report against Nephele in the new `.agents/acequia/issues/` namespace. 3. Establish that `acequia/issues/` is the right place for upstream-substrate bugs that aren't bead-scoped.
## Mechanism (what this bead does) - One-line normalization in [gallery.js:38-44](https://gsd.live/people/claudia-sachs/apps/collective-futures/js/gallery.js#L38-L44): rewrite each PROPFIND href as `new URL(text, location.origin).pathname` so subsequent fetches inherit the page's scheme. - A GitHub-issue-shaped `.md` filed at [acequia/issues/0001-nephele-propfind-http-scheme.md](https://redfish.acequia.io/guerin/acequia/issues/0001-nephele-propfind-http-scheme.md) describing the server-side bug, repro, and recommended fix. The server-side fix is out of scope for this bead — that work belongs in whichever bead picks up Nephele's href serialization.
## Folder layout ``` e3965679-df82-417b-9282-16289bfbb006/ ├── about.md ← this file └── 2026-06-04/ ├── chats/ │ └── 2026-06-04-collective-futures-propfind-http.md ├── notes/ (empty; analysis lives in the issue) ├── artifacts/ (empty) └── skills/ (empty) ```
## Session log - **2026-06-04** — Opened. Confirmed the PROPFIND bug with `curl`. Patched `gallery.js` (path-only). Filed Acequia issue `0001`.
## Modus operandi (how to interact) This bead is narrow and probably short-lived. If you're a future agent looking at this: - The patch is live in `gsd.live/people/claudia-sachs/apps/collective-futures/js/gallery.js`. If the Nephele server-side bug gets fixed, the patch is harmless (path-only still works) but the comment can be removed. - The issue file is the durable artifact. Update its `state` field to `closed` when Nephele ships the fix. - Do not promote this bead's directives into MEMORY.md — the bead's existence is local to this debugging episode. The lasting convention (that Acequia issues live at `.agents/acequia/issues/`) is what's worth remembering, and that belongs in a separate reference memory if Stephen decides to canonicalize it.
## Capabilities - Reproduce the PROPFIND bug with `curl -X PROPFIND -H "Depth: 1" https://gsd.live/...`. - Verify the client-side patch by loading the gallery page over HTTPS and watching the network tab — `result.json` requests should be HTTPS and load successfully.
## Lifecycle Active until Claudia confirms the gallery renders over HTTPS without console errors, then end-bead. The issue file outlives the bead.
## Limitations - Does not fix Nephele itself. That's filed and tracked separately. - Patch only covers `gallery.js`. Other apps that call PROPFIND directly (any in this ecology that depend on the href being usable as a fetch URL) will have the same bug and need the same one-line normalization.
See all: Beads