Opened 9 years ago

Closed 9 years ago

Last modified 21 months ago

#462 closed editorial (incorporated)

Editorial suggestions 2

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


  • 2.1 "A byte range operation MAY specify..." This is the only place "operation" is used in the document; it should either be defined, or replaced by another term.
  • 3.1 "...and only if the result of their evaluation is leading toward a 200 (OK) response." This is a bit informal...
  • 3.1 "If all of the preconditions are true, the server supports the Range header field for the target resource, and the specified range(s) are invalid or unsatisfiable, the server SHOULD send a 416 (Range Not Satisfiable) response."

Yet 4.4 says: "because servers are free to ignore Range, many implementations will simply respond with 200 (OK) if the requested ranges are invalid or not satisfiable."

I think sometimes responding with 200 is the right thing to do here sometimes, and so we shouldn't put a requirement against it. We could either remove the SHOULD, or qualify it with something that allows the server to make a judgement call.

  • 4.3 first paragraph re-defines what validator strength is; this should just be a reference to p4.
  • 4.3 last paragraph places a requirement on clients to "record" sets of ranges; how exactly do they meet this requirement? Terminology seems strange.

Change History (6)

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

  • Milestone changed from unassigned to 23
  • Owner changed from draft-ietf-httpbis-p5-range@… to julian.reschke@…

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

From [2296]:

s/operation/request/, also get rid of a useless "MAY" (see #462)

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

From [2297]:

adjust language describing why a server would not return 416, also s/record/process/ because we never say what "record" means (see #462)

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

From [2299]:

rephrase "...leading toward a 200..." (see #462)

comment:5 Changed 9 years ago by julian.reschke@…

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

comment:6 Changed 21 months ago by mnot@…

  • Summary changed from Editorial suggestions to Editorial suggestions 2
Note: See TracTickets for help on using tickets.