Opened 10 years ago

Closed 9 years ago

#465 closed design (fixed)

Mention 203 Non-Authoritative Information in p1

Reported by: mnot@… Owned by: draft-ietf-httpbis-p1-messaging@…
Priority: normal Milestone: 23
Component: p1-messaging Severity: In WG Last Call
Keywords: Cc:


We define 203 in p2 as being applicable when the content has been modified by an intermediary;

The 203 (Non-Authoritative Information) status code indicates that the request was successful but the enclosed payload has been modified from that of the origin server's 200 (OK) response by a transforming proxy (Section 5.7.2 of [Part1]). This status code allows the proxy to notify recipients when a transformation has been applied, since that knowledge might impact later decisions regarding the content. For example, future cache validation requests for the content might only be applicable along the same request path (through the same proxies).

However, 203 isn't mentioned anywhere in <>. It seems like it should either be mentioned as an appropriate thing to use there, or deprecated.

Change History (4)

comment:1 Changed 10 years ago by fielding@…

From [2287]:

Mention 203 (Non-Authoritative Information) in description of payload transformations; addresses #465

comment:2 Changed 10 years ago by fielding@…

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

comment:3 Changed 9 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:4 Changed 9 years ago by mnot@…

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