Parsing malformed HTTP dates
draft-hoehrmann-date-parsing-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Bjoern Hoehrmann | ||
| Last updated | 2010-09-20 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The HTTP/1.1 specification encourages recipients of date values, as found in HTTP headers like Date and Last-Modified, to be robust in accepting date values that may have been sent by non-HTTP software. This memo defines an error-tolerant parsing algorithm based on the date formats permitted by the HTTP specification for this purpose.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)