HTTP

Requests, responses, caching and CORS.

HTTP is taught here in 13 lessons, running from HTTP methods through to Debugging HTTP: tools, logs and observability. Each lesson takes one topic, shows the working code, and links onward to the next, so the course can be read straight through in order.

TrackBack-end Development
Lessons13
LevelBeginner to intermediate
Reading timeabout 3 hours
PrerequisitesHelpful, but not required: Java

Lessons

  1. HTTP methodsGET, POST, PUT, PATCH and DELETE — what each promises about safety, idempotency, and when to use it.
  2. HTTP status codesThe codes that actually matter in production — and the ones applications routinely get wrong.
  3. HTTP headersContent negotiation, auth, compression and security headers — the metadata that controls real behaviour.
  4. Caching and conditional requestsCache-Control in plain language, ETags versus Last-Modified, and revalidation with 304 responses.
  5. CORS explainedWhy the browser blocks cross-origin reads, how preflight works, and the headers that fix it properly.
  6. HTTPS and TLSWhat TLS actually protects, how certificates get validated, renewal automation, and mixed content traps.
  7. Message anatomy and framingRequest and response structure, start line and headers, Content-Length versus chunked transfer, trailers, and how HTTP/1.1, HTTP/2 and HTTP/3 differ on the wire.
  8. Cookies, sessions and stateSet-Cookie attributes, Domain, Path, Secure, HttpOnly and SameSite, session identifiers, third-party cookie restrictions, and storage alternatives.
  9. Authentication on the wireBasic and Digest, Bearer tokens and JWT structure, API keys, OAuth 2.1 flows and scopes, mutual TLS, and how WWW-Authenticate drives the flow.
  10. Compression, content negotiation and media typesAccept and Accept-Encoding with quality values, gzip, Brotli and zstd, charset handling, multipart uploads, and byte-range requests.
  11. Proxies, load balancers and connection managementForwarded and X-Forwarded headers, keep-alive and connection pooling, timeouts and retries, idempotency keys, and how CDNs and reverse proxies rewrite traffic.
  12. HTTP API design in practiceApplying method semantics, pagination strategies, ETags in APIs, problem-detail error bodies, versioning, webhooks and delivery guarantees.
  13. Debugging HTTP: tools, logs and observabilitycurl and API clients, browser network panel analysis, HAR capture, server access logs, tracing and correlation headers, Server-Timing, and a catalogue of common failure signatures.

More in Back-end Development

Node.js PHP Java Go Rust Spring Boot Laravel Ruby GraphQL

FAQ

How long does the HTTP course take?
It has 13 lessons, about 3 hours of reading. Expect roughly twice that if you type out and run every example.
Do I need prior experience for HTTP?
Not strictly. It helps to have read Java first, because some lessons build on it, but every lesson explains its own assumptions.
What should I read after HTTP?
Continue with Go (13 lessons), the next course in Back-end Development.

Last refreshed 2026-09-18.