Skip to content

Viewer proxy forwards only paths inside the /agentmemory/ prefix #36

Closed

Description

@possiblyneal

Parent

Part of #31.

Branch: fix/security

What to build

The viewer on the Operator's LAN-facing port refuses any request whose path, after URL normalization (dot segments resolved, percent-encoded dots and slashes decoded first), does not begin with /agentmemory/. Such requests are answered 404 locally and never reach the REST port, so the daemon secret is only ever attached to a request that passed the check.

Acceptance criteria

  • HTTP test with a fake upstream: /agentmemory/../other, /agentmemory/%2e%2e/other and a bare /other never reach upstream and get 404
  • A legitimate /agentmemory/health reaches upstream with the bearer attached
  • No request outside the prefix is ever observed carrying the bearer
  • npm test green

Blocked by

  • None — can start immediately

Activity

  1. possiblyneal commented on Sep 22, 2026

    @possiblyneal
    OwnerAuthor

    Closed by 29248bb on fix/security. Bare paths are 404 rather than rewritten; the viewer client always sends the prefix.

  2. added a commit that references this issue on Sep 22, 2026
    29248bb
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

    ready-for-agentFully specified, ready for an AFK agent

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions