HTTP Headers

They are metadata a web server returns with each response — things like Content-Type, Cache-Control, Server, Set-Cookie and security headers. They control caching, security and how browsers handle the page.

Yes. It shows the full redirect chain with the status code at each hop and the headers of the final response.

To debug caching, redirects, CORS, cookies and compression, and to confirm a server is returning the configuration you expect.

Cache-Control tells browsers and proxies how long to store a response and whether they may reuse it. Directives like max-age, no-cache and private control caching behavior and are key to performance tuning.

Both support conditional requests so a client can skip re-downloading unchanged content. Last-Modified uses a timestamp, while ETag uses an opaque version identifier that can detect changes more precisely.

Content-Encoding shows how the response body was compressed, such as gzip or br (Brotli). Compression reduces transfer size, and this header tells the browser how to decompress the payload.

Set-Cookie is how a server asks the browser to store a cookie, often for sessions or preferences. Inspecting it lets you confirm attributes like Secure, HttpOnly and SameSite are set correctly.