* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #248 (closed design: fixed)

Opened 4 years ago

Last modified 3 years ago

confusing Date requirements for clients

Reported by: julian.reschke@gmx.de Owned by: julian.reschke@gmx.de
Priority: normal Milestone: 12
Component: p1-messaging Severity: Active WG Document
Keywords: Cc:
Origin:

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

comment:1 Changed 4 years ago by julian.reschke@gmx.de

From [1047]:

rephrase client requirements for Date header field (addresses #248)

comment:2 Changed 4 years ago by julian.reschke@gmx.de

  • Status changed from new to closed
  • Resolution set to incorporated
  • Milestone changed from unassigned to 12

comment:3 Changed 3 years ago by mnot@pobox.com

  • Status changed from closed to reopened
  • Resolution incorporated deleted

comment:4 Changed 3 years ago by mnot@pobox.com

  • Status changed from reopened to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.