Use curl as the ground-truth HTTP client during recon and verification — browser-impersonation headers for CDN/WAF 403s, --globoff for bracket params, Windows curl.exe quirks, SPA false-200 traps. Load when bare tooling gets 403/blocked at a CDN edge, an API needs precise hand-crafted requests, or s
v2026.10.14-ee0e0c53 installazioni+3 in 7 giorni★ 27 StelleMITsincronizzato 22 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/tools-curl
Scrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
rE+18ROYpS…4fzhSMDw==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Any time you need to know what a server actually returns — no proxy magic, no scanner
interpretation — or when automated tooling is being blocked at a CDN/WAF edge and you suspect the
request shape, not the content, is the problem. Typical trigger: bare curl or a datacenter UA gets
403 with a JSON access-policy body or a CF-RAY header, while the same endpoint works in a real
browser.
Edge protection (Cloudflare & friends) classifies clients by TLS/HTTP fingerprints and headers. A
request carrying a browser User-Agent plus plausible Origin/Referer/Sec-Fetch-* headers often
sails through where a naked curl gets challenged — and unlike a scanner, curl shows you the exact
bytes that came back.
Match Origin/Referer to the site's real front-end origin — that's usually what the policy
keys on.
Bracket/query params (prototype-pollution shapes) need --globoff: curl treats [] as URL
globs and dies with curl: (3) bad range in position N. Either:bash
Still 403 and HTML contains Cf-Mitigated: challenge → a real browser or an authenticated
session is required; do not brute-force the edge.
SPA route that returns 200 with an identical body size for every path → front-end router,
not a real API hit — don't log it as an endpoint.
Feed curl requests to other tools: once a request works, export/replay it exactly — save it
for sqlmap -r (tools-sqlmap) or send it to Burp Repeater (tools-burp-suite) instead of
re-deriving it.
curl -I sends HEAD — some apps 405 or behave differently on HEAD; for a real GET with
headers shown, use curl -s -o /dev/null -D -.
Windows curl.exe vs the alias — in PowerShell curl may be an alias for
Invoke-WebRequest; call curl.exe explicitly, and remember --globoff for [].
Windows httpx collision — the httpx command may resolve to the Python httpx library CLI,
not ProjectDiscovery's httpx; check httpx -version before piping recon output into it.
A working browser-header bypass is recon, not a bypass finding — it means the edge admits
browser-shaped traffic; record it and continue, don't report it.
Timeouts are part of the command — always --max-time; a hung curl in an automated loop
silently stalls the whole pipeline.
You have a reproducible, copy-pasteable request that returns the expected status/body through the
edge, saved verbatim in the engagement notes so any later tool (sqlmap, Repeater, a finding's
repro steps) uses the exact same bytes.