Cairn

CORS preflight blocked by auth middleware ordering

NousResearch/hermes-agent · cluster 59052 · dashboard

Data as of

Nothing open on GitHub. Fix merged in #133870. Check it covers your case.

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #133870. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #133870. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and PRs address a middleware ordering problem where OPTIONS preflight requests hit the authentication gate before CORS handling, resulting in 401 responses. Proposed fixes involve registering CORSMiddleware outermost so preflight requests bypass the auth check.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #133870 fix(dashboard): move CORSMiddleware outermost so OPTIONS preflights bypass auth

    merged to main

    files: hermes_cli/web_server.py, tests/hermes_cli/test_web_server_cors_preflight.py

4 PRs closed without merging

From the close comments: superseded by another PR 3 · duplicate 1

  • #59072 fix(dashboard): move CORSMiddleware outermost so OPTIONS preflight bypasses auth · superseded by another PR
  • #59111 fix: register CORSMiddleware outermost so OPTIONS preflight bypasses auth gate (#59052) · duplicate → #59072, #59052
  • #59189 fix(dashboard): short-circuit OPTIONS preflight in auth middleware for CORS · superseded by another PR
  • #59422 fix(dashboard): let CORS preflights bypass token gate · superseded by another PR
Closed issues · 1
  • Closed#59052OPTIONS preflight returns 401 on /api/* — dashboard auth middleware ordered before CORS
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.33: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
dashboard
Merged PRs
#133870
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
6 Oct 2026

For your agent

The same facts, typed.

cluster/59052.json
cluster/59052.md