… Status Codes HTTP Status Codes Registration Procedure(s) IETF Review Reference RFC7231 Note 1xx: Informational - Request received, continuing process 2xx: Success - The action was successfully received, understood, and accepted 3xx: Redirection - Further action must be taken in …
…fication: "Message Syntax and Routing" (this document) "Semantics and Content" [RFC7231] "Conditional Requests" [RFC7232] "Range Requests" [RFC7233] "Caching" [RFC7234] "Authentication" [RFC7235] This HTTP/1.1 specification obsoletes RFC 2616 and RFC 2145 (on HTTP versioning). Th…
…n: 1. "Message Syntax and Routing" (this document) 2. "Semantics and Content" [ RFC7231 3. "Conditional Requests" [ RFC7232 4. "Range Requests" [ RFC7233 5. "Caching" [ RFC7234 6. "Authentication" [ RFC7235 This HTTP/1.1 specification obsoletes RFC 2616 and RFC 2145 (on HTTP vers…
…on: 1. "Message Syntax and Routing" (this document) 2. "Semantics and Content" [RFC7231] 3. "Conditional Requests" [RFC7232] 4. "Range Requests" [RFC7233] 5. "Caching" [RFC7234] 6. "Authentication" [RFC7235] This HTTP/1.1 specification obsoletes RFC 2616 and RFC 2145 (on HTTP ver…
…n: 1. "Message Syntax and Routing" (this document) 2. "Semantics and Content" [ RFC7231 3. "Conditional Requests" [ RFC7232 4. "Range Requests" [ RFC7233 5. "Caching" [ RFC7234 6. "Authentication" [ RFC7235 This HTTP/1.1 specification obsoletes RFC 2616 and RFC 2145 (on HTTP vers…
…n: 1. "Message Syntax and Routing" (this document) 2. "Semantics and Content" [ RFC7231 3. "Conditional Requests" [ RFC7232 4. "Range Requests" [ RFC7233 5. "Caching" [ RFC7234 6. "Authentication" [ RFC7235 This HTTP/1.1 specification obsoletes RFC 2616 and RFC 2145 (on HTTP vers…
…n: 1. "Message Syntax and Routing" (this document) 2. "Semantics and Content" [ RFC7231 3. "Conditional Requests" [ RFC7232 4. "Range Requests" [ RFC7233 5. "Caching" [ RFC7234 6. "Authentication" [ RFC7235 This HTTP/1.1 specification obsoletes RFC 2616 and RFC 2145 (on HTTP vers…
…n: 1. "Message Syntax and Routing" (this document) 2. "Semantics and Content" [ RFC7231 3. "Conditional Requests" [ RFC7232 4. "Range Requests" [ RFC7233 5. "Caching" [ RFC7234 6. "Authentication" [ RFC7235 This HTTP/1.1 specification obsoletes RFC 2616 and RFC 2145 (on HTTP vers…
…n: 1. "Message Syntax and Routing" (this document) 2. "Semantics and Content" [ RFC7231 3. "Conditional Requests" [ RFC7232 4. "Range Requests" [ RFC7233 5. "Caching" [ RFC7234 6. "Authentication" [ RFC7235 This HTTP/1.1 specification obsoletes RFC 2616 and RFC 2145 (on HTTP vers…
…the World Wide Web [ WEBARCH ] and Hyper-text Transfer Protocol ([ RFC7230 ], [ RFC7231 ], [ RFC7232 ]). Link A relationship between two resources when one resource (representation) refers to the other resource by means of a URI [ WEBARCH ]. Linked Data As defined by Tim Berners-…
…the World Wide Web [ WEBARCH ] and Hyper-text Transfer Protocol ([ RFC7230 ], [ RFC7231 ], [ RFC7232 ]). Link A relationship between two resources when one resource (representation) refers to the other resource by means of a URI [ WEBARCH ]. Linked Data As defined by Tim Berners-…
…e Operation Proper cache operation preserves the semantics of HTTP transfers ( [RFC7231] ) while eliminating the transfer of information already held in the cache. Although caching is an entirely OPTIONAL feature of HTTP, it can be assumed that reusing a cached response is desira…
…e Operation Proper cache operation preserves the semantics of HTTP transfers ([ RFC7231 ]) while eliminating the transfer of information already held in the cache. Although caching is an entirely OPTIONAL feature of HTTP, it can be assumed that reusing a cached response is desira…
…e Operation Proper cache operation preserves the semantics of HTTP transfers ([ RFC7231 ]) while eliminating the transfer of information already held in the cache. Although caching is an entirely OPTIONAL feature of HTTP, it can be assumed that reusing a cached response is desira…
…e Operation Proper cache operation preserves the semantics of HTTP transfers ([ RFC7231 ]) while eliminating the transfer of information already held in the cache. Although caching is an entirely OPTIONAL feature of HTTP, it can be assumed that reusing a cached response is desira…
Page 1
Next →