Opened 7 years ago

Closed 7 years ago

#296 closed design (fixed)

Clarify 203 Non-Authoritative Information

Reported by: mnot@… Owned by: draft-ietf-httpbis-p2-semantics@…
Priority: normal Milestone: 15
Component: p2-semantics Severity: Active WG Document
Keywords: Cc:

Description

The 203 status code's definition is vague; it could lead some people to believe that it's appropriate for any cached response.

Proposal:

8.2.4. 203 Non-Authoritative Information

The representation in the response has been transformed or otherwise modified by a non-transparent proxy [ref to p1]. Note that the behaviour of transforming intermediaries is controlled by the no-transform Cache-Control dirctive [ref to p6].

This status code is only appropriate when the response status code would have been 200 (OK). When the status code before transformation would have been different, the 214 Transformation Applied warn-code [ref] is appropriate.

Caches MAY use a heuristic (see Section 2.3.1.1 of [Part6]) to determine freshness for 203 responses.

Attachments (1)

296.diff (4.8 KB) - added by julian.reschke@… 7 years ago.

Download all attachments as: .zip

Change History (5)

Changed 7 years ago by julian.reschke@…

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

From [1309]:

Clarify 203 Non-Authoritative Information (see #296)"

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

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

comment:3 Changed 7 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:4 Changed 7 years ago by mnot@…

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