Network & Domain

HTTP Header Inspector

Inspect response headers returned by a public website.

Read the guide

Run the tool

JVR Software’s server processes the public target you enter. The diagnostic is rate-limited. Use a system you own or are authorised to check.

More information

Back to the tool

What it is and when to use it

HTTP Header Inspector shows the response metadata a public site sends before its page content. Use it to diagnose the wrong file type, an unexpected cache setting, a missing content disposition for a download, or differences between two pages on a site you operate.

How it works

JVR Software makes a bounded GET request and presents the HTTP status plus the response headers exposed by its HTTP client. It may follow redirects before receiving the response it reports. A response header describes what the server, proxy or CDN chose to send for that request.

How to use it

  1. Enter the full URL including the exact path.
  2. Run the inspector and look for the header relevant to your question, such as Content-Type, Cache-Control or Content-Disposition.
  3. Test the exact page that fails and compare it with a working page using the same request conditions.

Worked example

A CSS URL that returns text/html may be serving a login page or error document. A content type of text/css is expected for a stylesheet. Inspect the HTTP status as well so you do not treat the correct type on an error page as a pass.

Reading the result

Header names are case insensitive. Several values can appear for a single field, and headers from a redirect can differ from the final response. Headers such as Age and Cache-Control can give clues about caching, although their presence alone does not establish how a particular CDN behaved.

When diagnosing stale content, compare Cache-Control, Age and any validator fields such as ETag in two responses. Browser caches, a CDN and the origin can each influence what you see. Keep the exact requested URL and timestamp with the response so you can compare like for like.

Common mistakes and limits

The inspector does not use your browser cookies or reproduce a signed-in request. Some response headers can contain identifiers such as session cookies. Redact those values before sharing results. Use your browser's network inspector to compare a request that depends on login or a particular browser.