Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#48 closed editorial (fixed)

Date reference typo

Reported by: mnot@… Owned by:
Priority: Milestone: 01
Component: p1-messaging Severity:
Keywords: Cc:

Description

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."

Change History (4)

comment:1 Changed 10 years ago by mnot@…

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:2 Changed 10 years ago by fielding@…

  • Component set to messaging
  • Resolution set to fixed
  • Status changed from new to closed

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

comment:3 Changed 10 years ago by fielding@…

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

comment:4 Changed 10 years ago by mnot@…

  • Milestone set to 01
Note: See TracTickets for help on using tickets.