#165 closed design (fixed)
Case-sensitivity of HTTP-date
Reported by: | julian.reschke@… | Owned by: | fielding@… |
---|---|---|---|
Priority: | urgent | Milestone: | 10 |
Component: | p1-messaging | Severity: | Active WG Document |
Keywords: | Cc: |
Description
RFC 2616, Section 3.3.1 is ambiguous with respect to *parsing* requirements for HTTP dates.
It says:
"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.
Attachments (1)
Change History (10)
comment:1 Changed 14 years ago by fielding@…
- Milestone changed from unassigned to 08
- Owner set to fielding@…
- Priority set to urgent
- Status changed from new to assigned
comment:2 Changed 13 years ago by julian.reschke@…
- Milestone changed from 08 to 09
comment:3 Changed 13 years ago by julian.reschke@…
- Milestone changed from 09 to 10
comment:4 Changed 13 years ago by julian.reschke@…
Proposal:
leave ABNF as it is
say "clients are REQUIRED" instead of "encouraged"
comment:5 Changed 13 years ago by julian.reschke@…
comment:6 Changed 13 years ago by julian.reschke@…
- Resolution set to incorporated
- Status changed from assigned to closed
comment:7 Changed 12 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:8 Changed 12 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
comment:9 Changed 11 years ago by mnot@…
- Severity changed from Candidate WG Document to Active WG Document
It is not ambiguous to require one thing and suggest reasonable error handling.