Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#461 closed editorial (incorporated)

Editorial suggestions

Reported by: mnot@… Owned by: julian.reschke@…
Priority: normal Milestone: 23
Component: p4-conditional Severity: In WG Last Call
Keywords: Cc:

Description (last modified by julian.reschke@…)

* 2.1 "...avoid confusing cache behaviour." It's not just caches; suggest "...avoid undesired behaviour."

  • 3.1 "...instead they MUST respond with the 412 (Precondition Failed) status code." This is too strong; e.g., what if authentication is needed? Suggest an "unless..." clause allowing other error status codes.

* 3.2 needs a references to "unsafe" in p2.

  • 3.4 same problem with MUST respond as 3.1.
  • 5 Paragraphs two and three repeat what's been said previously in the document; are they necessary?

Change History (4)

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

From [2230]:

editorial improvements (see #461)

comment:2 Changed 6 years ago by julian.reschke@…

  • Description modified (diff)
  • Owner changed from draft-ietf-httpbis-p4-conditional@… to julian.reschke@…

comment:3 Changed 6 years ago by julian.reschke@…

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

Closing this one; leaving 3.1, 3.4 and 5 alone.

comment:4 Changed 6 years ago by julian.reschke@…

  • Milestone changed from unassigned to 23
Note: See TracTickets for help on using tickets.