Opened 10 years ago

Closed 9 years ago

Last modified 9 years ago

#301 closed design (fixed)

Content-Range on responses other than 206

Reported by: mnot@… Owned by: ylafon@…
Priority: normal Milestone: 17
Component: p5-range Severity: Active WG Document
Keywords: Cc:

Description

We should clarify that Content-Range has no meaning on responses that aren't 206's.

Background:

​http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=45116

Change History (8)

comment:1 Changed 10 years ago by mnot@…

  • Owner changed from draft-ietf-httpbis-p5-range@… to mnot@…
  • Status changed from new to assigned

comment:2 Changed 10 years ago by mnot@…

  • Milestone changed from unassigned to 16
  • Owner changed from mnot@… to ylafon@…
  • Status changed from assigned to new

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

  • Milestone changed from 16 to 17

comment:4 Changed 10 years ago by ylafon@…

From [1459]:

Clarify that Content-Range has no meaning for status codes not explicitly allowing it (206, 416) This addresses #301

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

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

comment:6 Changed 9 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:7 Changed 9 years ago by mnot@…

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

comment:8 Changed 9 years ago by mnot@…

  • Severity changed from Candidate WG Document to Active WG Document
Note: See TracTickets for help on using tickets.