Challenge 2: Diagnose Missing Output — Possible Solution
====================================================================

MOST LIKELY EXPLANATION: the URL is redirecting (a 3xx response with a
Location header) to a different URL that actually holds the data, and
curl — by default — does NOT follow redirects. Instead of an error, it
simply prints whatever the redirect response's own body contains,
which for many redirect responses is empty or a short generic message,
looking exactly like "no data" even though the real report lives one
hop away.

THE FLAG TO CONFIRM IT: -i (or -iL together). Running
curl -i https://api.example.com/old-report would reveal a status code
in the 3xx range along with a Location header pointing at where the
data actually lives — confirming the redirect theory directly, since
the default (bodies-only) output gives no visibility into the status
code or headers at all.

THE FIX: add -L to make curl follow the redirect automatically —
curl -iL https://api.example.com/old-report — which should then show
the real report data from the final destination.