Ticket #165 (closed design: fixed)
Case-sensitivity of HTTP-date
|Reported by:||firstname.lastname@example.org||Owned by:||email@example.com|
|Component:||p1-messaging||Severity:||Active WG Document|
RFC 2616, Section 3.3.1 is ambiguous with respect to *parsing* requirements for HTTP dates.
"HTTP-date is case sensitive and MUST NOT include additional LWS beyond that specifically included as SP in the grammar."
but then also points out:
"Note: Recipients of date values are encouraged to be robust in accepting date values that may have been sent by non-HTTP applications, as is sometimes the case when retrieving or posting messages via proxies/gateways to SMTP or NNTP."
Brian Smith points out that the dates are case-insensitive in SMPT and NNTP.
"...are encouraged..." isn't using BCP 14 terminology. So is this a SHOULD-level requirement? A MAY?
If it is a SHOULD, HTTPbis will need to rephrase the statement about case-insensitivity, and adjust the ABNF which in the meanwhile uses case-sensitive day and month names.
- Owner set to firstname.lastname@example.org
- Priority set to urgent
- Status changed from new to assigned
- Milestone changed from unassigned to 08
- Status changed from assigned to closed
- Resolution set to incorporated
- Status changed from closed to reopened
- Resolution incorporated deleted
- Status changed from reopened to closed
- Resolution set to fixed