Issues

Bound response-body memory during assertion evaluation
korya/http-assert#106 · opened on Aug 31, 2026
Two blank lines precede every Error: line
korya/http-assert#100 · opened on Aug 11, 2026
A one-line assertion failure costs 20 lines; there is no concise output mode
korya/http-assert#99 · opened on Aug 11, 2026
Internal Go and library error strings leak into user-facing messages
korya/http-assert#96 · opened on Aug 11, 2026
--log-level debug is identical to info, so -v changes nothing
korya/http-assert#95 · opened on Aug 11, 2026
Unsupported scheme and empty URL exit 92 though no request was attempted
korya/http-assert#94 · opened on Aug 11, 2026
Response body in the failure dump is truncated at 256 bytes with no marker
korya/http-assert#92 · opened on Aug 11, 2026
1
Assertion failure message embeds the entire response body, unbounded
korya/http-assert#91 · opened on Aug 11, 2026
1
Feature: machine-readable output (--json)
korya/http-assert#45 · opened on Aug 7, 2026
Feature: authentication support (-u basic auth, --cookie, bearer tokens)
korya/http-assert#44 · opened on Aug 7, 2026
Feature: --assert-time to assert response latency
korya/http-assert#42 · opened on Aug 7, 2026
Cobra's auto-generated completion subcommand is undocumented and shadows the URL argument
korya/http-assert#36 · opened on Aug 7, 2026
All output goes to stderr; stdout is always empty
korya/http-assert#34 · opened on Aug 7, 2026
--max-time accepts 0 and negative values without validation
korya/http-assert#31 · opened on Aug 7, 2026
1
--maphost discards its own specific parse error
korya/http-assert#26 · opened on Aug 7, 2026
Wildcard --maphost values (* and *:*) are unreachable from the CLI
korya/http-assert#23 · opened on Aug 7, 2026