…onal Requests June 2014 . Introduction Conditional requests are HTTP requests [ RFC7231 ] that include one or more header fields indicating a precondition to be tested before applying the method semantics to the target resource. This document defines the HTTP/1.1 conditional requ…
…aders, using the ABNF [ RFC5234 ] syntax defined in Section 5.3.2 of HTTP/1.1 [ RFC7231 ], is given by the following definition: Accept-Post = #( media-range [ accept-params ] ) (Please note that this ABNF differs from the one given in Section 5.3.2 of RFC 7231 RFC7231 ], which i…
…S query. A successful HTTP response with a 2xx status code (see Section 6.3 of [RFC7231] ) is used for any valid DNS response, regardless of the DNS response code. For example, a successful 2xx HTTP status code is used even with a DNS message whose DNS response code indicates fai…
…gful substructure for any representation transferable over HTTP ( Section 3 of [RFC7231] ). The "bytes" range unit is defined for expressing subranges of the data's octet sequence. bytes-unit = "bytes" A byte-range request can specify a single range of bytes or a set of ranges wi…
…ngful substructure for any representation transferable over HTTP (Section 3 of [RFC7231]). The "bytes" range unit is defined for expressing subranges of the data's octet sequence. bytes-unit = "bytes" A byte-range request can specify a single range of bytes or a set of ranges wit…
…tiation, if the Accept-Language header field has been set in the HTTP request [ RFC7231 ]. The APIs set the HTTP status codes as defined in Section 6 of [ RFC7231 ]. The list of used error codes include (but are not limited to) the following: 400 (Bad Request): Invalid client inp…
…in 0-RTT. ACME clients MUST send a User-Agent header field, in accordance with [RFC7231]. This header field SHOULD include the name and version of the ACME software in addition to the name and version of the underlying HTTP client software. Barnes, et al. Standards Track [Page 10…
…t for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4 ). o "status" (number) - The HTTP status code ( [RFC7231], Section 6 generated by the origin server for this occurrence of the problem. o "detail" (string) - A human-readable exp…
…f [ RFC7230 ]; as well as the "delta-seconds" rule defined in Section 8.1.3 of [RFC7231] . The Prefer Request Header Field The Prefer request header field is used to indicate that particular server behaviors are preferred by the client but are not required for successful completi…
… include "GET", "HEAD", "OPTIONS", and "TRACE", as defined in Section 4.2.1 of [RFC7231]. A domain's "public suffix" is the portion of a domain that is controlled by a public registry, such as "com", "co.uk", and "pvt.k12.wy.us". A domain's "registrable domain" is the domain's pu…
…er field is the URL of the representation it is associated with, as defined in [RFC7231], Section 3.1.4.1 , and is serialised as a URI. When present, the anchor parameter overrides this with another URI, such as a fragment of this resource, or a third resource (i.e., when the anc…
…er field is the URL of the representation it is associated with, as defined in [RFC7231] , Section 3.1.4.1, and is serialised as a URI. When present, the anchor parameter overrides this with another URI, such as a fragment of this resource, or a third resource (i.e., when the anc…
…er field is the URL of the representation it is associated with, as defined in [RFC7231], Section 3.1.4.1 , and is serialised as a URI. When present, the anchor parameter overrides this with another URI, such as a fragment of this resource, or a third resource (i.e., when the anc…
…gful substructure for any representation transferable over HTTP ( Section 3 of [RFC7231] ). The "bytes" range unit is defined for expressing subranges of the data's octet sequence. bytes-unit = "bytes" A byte-range request can specify a single range of bytes or a set of ranges wi…
…of the World Wide Web [ WEBARCH ], Hyper-text Transfer Protocol ([ RFC7230 ], [ RFC7231 ]) and Linked Data Platform [ LDP ]. Paged resource LDPR whose representation may be too large for a server to construct in a single HTTP response (e.g. without running out of memory), for whi…