httpbis: Ticket #48: Date reference typo

Link:  http://trac.tools.ietf.org/wg/httpbis/trac/ticket/48

Origin:  http://www.w3.org/mid/4561B971.1090805@gmx.de

Component: p1-messaging

Currently, RFC2616 says about the date format for the "Date" header:

"The field value is an HTTP-date, as described in section 3.3.1; it MUST be sent in RFC 1123 [8]-date format."

Mails

• NEW ISSUE: typo (?) in 14.18, rfc1123-format Julian Reschke (julian.reschke@gmx.de) (2006-11-20)
  • Re: NEW ISSUE: typo (?) in 14.18, rfc1123-format Henrik Nordstrom (hno@squid-cache.org) (2006-11-29)
    • Re: NEW ISSUE: typo (?) in 14.18, rfc1123-format Julian Reschke (julian.reschke@gmx.de) (2006-11-30)
  • Re: NEW ISSUE: typo (?) in 14.18, rfc1123-format Mark Nottingham (mnot@mnot.net) (2006-11-30)

Associated Checkins

mnot@pobox.com (Sat, 22 Dec 2007 02:30:21 GMT)

[8]: RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1 Translated from text to ...

fielding@gbiv.com (Mon, 24 Dec 2007 09:03:24 GMT)

[83]: Resolve #48: Date reference typo

[100]: Second part of resolution for #48: Date reference typo

History

: comment added (Sat, 22 Dec 2007 02:30:21 GMT)

Proposal: "The field value is an HTTP-date, as described in section 3.3.1; it MUST be sent in rfc1123-date [8] format."

: comment added; resolution, component set; status changed (Mon, 24 Dec 2007 09:03:24 GMT)

• status changed from new to closed.
• resolution set to fixed
• component set to messaging

Fixed in [83] and [100]. However, the fixed wording remains problematic in that the MUST requirement has no basis in reality.

: comment added (Mon, 24 Dec 2007 09:15:15 GMT)

See related design issue #51 for tracking the MUST requirement.

: comment added; milestone set (Fri, 04 Jan 2008 06:20:09 GMT)

• milestone set to 01

Related Information

Issues List Index