Opened 12 years ago
Closed 12 years ago
#248 closed design (fixed)
confusing Date requirements for clients
Reported by: | julian.reschke@… | Owned by: | julian.reschke@… |
---|---|---|---|
Priority: | normal | Milestone: | 12 |
Component: | p1-messaging | Severity: | Active WG Document |
Keywords: | Cc: |
Description
9.3 Date:
"Clients SHOULD only send a Date header field in messages that include a payload, as is usually the case for PUT and POST requests, and even then it is optional. A client without a clock MUST NOT send a Date header field in a request."
This is so wrong, spec-wise.
I think just removing the whole paragraph will make the spec better.
Change History (4)
comment:1 Changed 12 years ago by julian.reschke@…
comment:2 Changed 12 years ago by julian.reschke@…
- Milestone changed from unassigned to 12
- Resolution set to incorporated
- Status changed from new to closed
comment:3 Changed 12 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:4 Changed 12 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
Note: See
TracTickets for help on using
tickets.
From [1047]:
rephrase client requirements for Date header field (addresses #248)