Sanitize error headers containing control characters

NousResearch/hermes-agent · cluster 133848 · gateway

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

A bug was identified where newline or other control characters in agent error messages corrupt HTTP response headers. Related fixes address sanitizing these characters in the API server and gateway error headers.

Open issues1

  • Issue#133848[Bug]: API server drops the connection when an agent error message contains a newline (X-Hermes-Error header)

Open PRs2

  • PR#133872fix(api-server): fold control characters out of the X-Hermes-Error header
  • PR#136580fix(api-server): fold control characters out of _redact_api_error_text

1 PR closed without merging

From the close comments: duplicate 1

  • #134317 fix(gateway): sanitize API error response headers · duplicate → #133872
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.50: 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
gateway
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.