#163 closed editorial (fixed)
editorial improvements around HTTP-date
Reported by: | julian.reschke@… | Owned by: | julian.reschke@… |
---|---|---|---|
Priority: | urgent | Milestone: | unassigned |
Component: | p1-messaging | Severity: | Active WG Document |
Keywords: | Cc: |
Description (last modified by julian.reschke@…)
Attachments (1)
Change History (11)
Changed 14 years ago by julian.reschke@…
comment:1 Changed 14 years ago by julian.reschke@…
comment:2 Changed 14 years ago by julian.reschke@…
comment:3 Changed 14 years ago by julian.reschke@…
comment:4 Changed 13 years ago by julian.reschke@…
- Priority set to urgent
Proposal: state that two digit dates have been and continue to be ambiguous and implementations differ.
comment:5 Changed 13 years ago by julian.reschke@…
- Owner set to julian.reschke@…
- Status changed from new to assigned
The two-digit-year issue is already mentioned in Appendix A:
"HTTP/1.1 clients and caches SHOULD assume that an RFC-850 date which appears to be more than 50 years in the future is in fact in the past (this helps solve the "year 2000" problem)."
Thus I propose to close this issue now.
comment:6 Changed 12 years ago by julian.reschke@…
- Resolution set to incorporated
- Status changed from assigned to closed
comment:7 Changed 12 years ago by julian.reschke@…
- Description modified (diff)
comment:8 Changed 12 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:9 Changed 12 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
comment:10 Changed 11 years ago by mnot@…
- Severity changed from Candidate WG Document to Active WG Document
Note: See
TracTickets for help on using
tickets.
proposed change for part 1