Learning HTTP by building a tiny client instead of another full-stack app

I understand what a web page does but HTTP still feels abstract: requests, headers, status codes and JSON appear in tutorials as though everyone already knows them. Rather than build another full-stack app, I'm thinking of writing a tiny command-line client that fetches a public endpoint, inspects responses and handles errors. What sequence of experiments would make HTTP click without pulling in a web framework?