2015-11-06 21:39:33 +01:00
|
|
|
---
|
|
|
|
|
set: 2
|
|
|
|
|
code: 203
|
2015-11-07 02:41:41 +01:00
|
|
|
title: Non-authoritative Information
|
|
|
|
|
references:
|
|
|
|
|
"Rails HTTP Status Symbol": ":non_authoritative_information"
|
2015-11-06 21:39:33 +01:00
|
|
|
---
|
|
|
|
|
|
2015-11-07 02:41:41 +01:00
|
|
|
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)](/200) response by a transforming proxy
|
2015-11-07 04:03:35 +01:00
|
|
|
([Section 5.7.2 of RFC7230][2]). This status code allows the proxy to notify
|
2015-11-07 02:41:41 +01:00
|
|
|
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).
|
|
|
|
|
|
|
|
|
|
The 203 response is similar to the Warning code of 214 Transformation Applied
|
2015-11-07 04:03:35 +01:00
|
|
|
([Section 5.5 of RFC7234][3]), which has the advantage of being applicable to
|
2015-11-07 02:41:41 +01:00
|
|
|
responses with any status code.
|
|
|
|
|
|
|
|
|
|
A 203 response is cacheable by default; i.e., unless otherwise indicated by the
|
|
|
|
|
method definition or explicit cache controls
|
2015-11-07 04:03:35 +01:00
|
|
|
(see [Section 4.2.2 of RFC7234][4]).
|
2015-11-07 02:41:41 +01:00
|
|
|
|
2015-11-07 04:03:35 +01:00
|
|
|
Source: [RFC7231 Section 6.3.4][1]
|
2015-11-07 02:41:41 +01:00
|
|
|
|
2015-11-07 04:03:35 +01:00
|
|
|
[1]: <http://tools.ietf.org/html/rfc7231#section-6.3.4>
|
|
|
|
|
[2]: <http://tools.ietf.org/html/rfc7230#section-5.7.2>
|
|
|
|
|
[3]: <http://tools.ietf.org/html/rfc7234#section-5.5>
|
|
|
|
|
[4]: <http://tools.ietf.org/html/rfc7234#section-4.2.2>
|
