1001Ferramentas
🕒Validators

Last-Modified Header Validator

Validate whether an HTTP Last-Modified header is in the correct format (HTTP-date, RFC 7231). Useful for debugging browser cache, CDNs and website performance.

Result

The exact format of Last-Modified

The Last-Modified header states when the resource last changed, and it underpins conditional revalidation: the client stores the date and, on the next visit, asks whether anything changed since. If nothing did, the response is short and bodiless. But the date format is rigid, and a date the client cannot parse makes all that saving disappear.

Paste the value and the page validates it against the required format: abbreviated English weekday, comma, two-digit day, abbreviated English month, four-digit year, time, and the literal GMT. None of that is negotiable — not the language, not the leading zeros, not the zone, which is always GMT even when the server sits elsewhere.

Three historical formats were once accepted, and the current specification says to generate only this one and accept the other two when reading, for compatibility. In practice, a server generating an old format meets a client that will not parse it, and revalidation quietly stops working — no error, just the resource being downloaded in full every time.

Frequently asked questions

Why is the zone always GMT?
To remove ambiguity: with a variable zone, comparing dates would require every client to know every daylight saving rule everywhere. Fixing GMT turns comparison into subtraction. The name GMT is used by tradition, though technically UTC is the correct term today.
Last-Modified or ETag?
The ETag is more precise: it identifies the content version rather than the moment of last change, avoiding two problems — one-second resolution, which misses rapid changes, and files regenerated with identical content and a new date. Ideally send both; if only one, prefer the ETag.
Can the date be in the future?
It should not be, and a client encountering that usually ignores the header. A future date normally means a skewed server clock or generation from the wrong metadata. The practical effect is revalidation ceasing to work for that resource.

Related Tools