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

Ticket #296 (closed design: fixed)

Opened 4 years ago

Last modified 3 years ago

Clarify 203 Non-Authoritative Information

Reported by: mnot@pobox.com Owned by: draft-ietf-httpbis-p2-semantics@tools.ietf.org
Priority: normal Milestone: 15
Component: p2-semantics Severity: Active WG Document
Keywords: Cc:
Origin: http://www.w3.org/mid/B9919A0D-3B6E-499A-9286-CB7FF54FF886@mnot.net


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


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 of [Part6]) to determine freshness for 203 responses.


296.diff (4.8 KB) - added by julian.reschke@gmx.de 4 years ago.

Change History

Changed 4 years ago by julian.reschke@gmx.de

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

From [1309]:

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

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

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

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.