HarperFast / HarperFast/harper
[Epic] HTTP error-hygiene (500-vs-4xx / info-leak)
Open
- Dominant language
- JavaScript
- Stars
- 89
- Forks
- 10
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 200
Description
Tracking epic for malformed/edge-case HTTP requests that return a 500 instead of a clean 4xx, sometimes leaking internal error details or persisting bad data.
---
_Filed by Claude (Opus 4.8), issue-backlog triage & grouping pass._
Contributor guide
Research direction
This is a tracking epic rather than a self-contained task, and it names no files, tests, or entry points. Start by enumerating the malformed and edge-case HTTP requests covered by the epic and their current responses. Done means each affected request returns a clean 4xx, does not leak internal error details, and does not persist bad data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api, backend, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100