curl commands you actually need on a server
Check status codes, follow redirects, time requests, send JSON, upload, resume downloads and fail properly in scripts, all tested against a local lab server.
Filtering by topic #http · clear
Check status codes, follow redirects, time requests, send JSON, upload, resume downloads and fail properly in scripts, all tested against a local lab server.
A web server can mean the machine or the program that answers HTTP requests. Run one with Python and one with nginx on localhost, then read the real headers.
HTTP explained for people who run servers: methods, status codes, the headers that matter, what nginx logs, and where HTTP/3 and TLS fit in.
How a one-line GET request became HTTP/3, with the real RFC dates and authors, and where each decision still shows on your own server today.
Anyone on the network path can read and change an http page. Learn when that risk is real, and what Chrome's warnings and the Chrome 154 change mean.
Three version numbers in one nginx config. What HTTP/2 multiplexing and HTTP/3 over QUIC actually change, how to enable each, and when it is worth it.
HTTP and HTTPS differ on the server side: a second listener, a redirect, HSTS you cannot easily undo, mixed content, and renewal that fails at 3am.
MCP revision 2026-07-28 removed sessions and the initialize handshake. What that means for your reverse proxy, health checks, timeouts and auth.