Skip to content

http.get silently drops the headers it documents #3

Closed

Description

@mberrishdev

docs/WidgetAPI.md documents await notchly.http.get(url, headers), and ui/lib/widget-runtime.js sends them:

get: (url, headers) => post("http.get", { url, headers }),

core/src/bridge.rs then ignores the parameter entirely:

let response = reqwest::get(&url).await.map_err(|error| error.to_string())?;

Every widget that authenticates against an API therefore fails, and fails in a way that looks like the widget author's fault rather than a missing capability. This blocks the whole category of token-based widgets.

Build a reqwest::Client request instead and apply the headers map. Worth rejecting or stripping hop-by-hop headers rather than forwarding whatever a widget asks for.

Activity

  1. added
    bugSomething isn't working
    widget-apiThe window.notchly bridge surface
    on Sep 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingwidget-apiThe window.notchly bridge surface

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions