HTTP headers, status codes and redirects, explained.
A header is a short line of information that travels alongside a web page but never shows up on the page itself: the server type, how long a browser should cache the file, whether the content is...
Read moreYou ran a page through a header checker, or scrolled through Search Console's Crawl Stats report, and there it is: HTTP status code 304. It's sitting in a list next to 301s and 302s, and your...
Read moreA 308 redirect isn't a fancier version of a 301. It solves a problem the 301 was never built to solve: keeping a POST, PUT, or DELETE request intact after your server tells the client to go...
Read moreTTFB stands for Time to First Byte, and if you are reading this, a speed report probably just flagged yours in red. That is usually the moment people start searching for a plain answer to what is...
Read moreYou typed in a web address you've visited a hundred times, and instead of your homepage you got a wall of text: "This page isn't working. example.com redirected you too many times." Or maybe...
Read moreYou ran a page through a header checker, or you opened DevTools and looked at the Network tab, and there it was: a Cache-Control header you didn't write, sitting on a response you own. Maybe it...
Read more
