Opened 14 years ago

Closed 14 years ago

#126 closed editorial (fixed)

bogus 2068 Date header reference

Reported by: julian.reschke@… Owned by:
Priority: Milestone: 04
Component: p4-conditional Severity: Active WG Document
Keywords: Cc:


Part 4, Section 4.1:

"If a clockless origin server obeys these rules, and proxies and clients add their own Date to any response received without one (as already specified by [RFC2068], Section 14.19), caches will operate correctly."

RFC2068, Section 14.19 is the definition of the Date header. Why does RFC2616 refer to RFC2068 instead to itself?

Proposal to reference Part 1, Sexction 8.3 instead.

Change History (1)

comment:1 Changed 14 years ago by julian.reschke@…

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

Fixed in [306]:

Resolve #126: use current Date header reference instead of pointing to RFC2068 (closes #126).

Note: See TracTickets for help on using tickets.