RFC2616. RFC 7235 - Hypertext Transfer Protocol (HTTP/1.1): Authentication. [Docs] [txt|pdf] [draft-ietf-httpbi...] [Diff1] [Diff2] [IPR] PROPOSED STANDARD Internet Engineering Task Force (IETF) R. Fielding, Ed. Request for Comments: 7235 Adobe Obsoletes: 2616 J. RFC 7235 HTTP/1.1 Authentication June 2014 material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. RFC 7235 HTTP/1.1 Authentication June 2014 1. HTTP provides a general framework for access control and authentication, via an extensible set of challenge-response authentication schemes, which can be used by a server to challenge a client request and by a client to provide authentication information. 1.1.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 1.2. 2. 2.1. RFC 7235 HTTP/1.1 Authentication June 2014 authentication via that scheme. 2.2. 3. 3.1. 401 Unauthorized 4. 4.1.
RFC 7234 - Hypertext Transfer Protocol (HTTP/1.1): Caching. [Docs] [txt|pdf] [draft-ietf-httpbi...] [Diff1] [Diff2] PROPOSED STANDARD Internet Engineering Task Force (IETF) R. Fielding, Ed. Request for Comments: 7234 Adobe Obsoletes: 2616 M. RFC 7234 HTTP/1.1 Caching June 2014 Copyright Notice Copyright (c) 2014 IETF Trust and the persons identified as the document authors. RFC 7234 HTTP/1.1 Caching June 2014 4.3.3. RFC 7234 HTTP/1.1 Caching June 2014 1. HTTP is typically used for distributed information systems, where performance can be improved by the use of response caches. 1.1. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 1.2.
RFC 7234 HTTP/1.1 Caching June 2014 repetition). 1.2.1. 2. Proper cache operation preserves the semantics of HTTP transfers ([RFC7231]) while eliminating the transfer of information already held in the cache. 3. RFC 7233 - Hypertext Transfer Protocol (HTTP/1.1): Range Requests. [Docs] [txt|pdf] [draft-ietf-httpbi...] [Diff1] [Diff2] PROPOSED STANDARD Internet Engineering Task Force (IETF) R. Fielding, Ed. Request for Comments: 7233 Adobe Obsoletes: 2616 Y. Lafon, Ed. Category: Standards Track W3C ISSN: 2070-1721 J. Reschke, Ed. greenbytes June 2014 Abstract The Hypertext Transfer Protocol (HTTP) is a stateless application- level protocol for distributed, collaborative, hypertext information systems.
RFC 7233 HTTP/1.1 Range Requests June 2014 Copyright Notice Copyright (c) 2014 IETF Trust and the persons identified as the document authors. RFC 7233 HTTP/1.1 Range Requests June 2014 Table of Contents 1. RFC 7233 HTTP/1.1 Range Requests June 2014 1. Hypertext Transfer Protocol (HTTP) clients often encounter interrupted data transfers as a result of canceled requests or dropped connections. 1.1. 1.2. RFC 7233 HTTP/1.1 Range Requests June 2014 2. 2.1. 2.2. Range units are intended to be extensible. 2.3. RFC 7233 HTTP/1.1 Range Requests June 2014 3. 3.1. 3.2. RFC 7232 - Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests. [Docs] [txt|pdf] [draft-ietf-httpbi...] [Diff1] [Diff2] PROPOSED STANDARD Internet Engineering Task Force (IETF) R. Fielding, Ed. Request for Comments: 7232 Adobe Obsoletes: 2616 J.
Reschke, Ed. Category: Standards Track greenbytes ISSN: 2070-1721 June 2014 Abstract The Hypertext Transfer Protocol (HTTP) is a stateless application- level protocol for distributed, collaborative, hypertext information systems. RFC 7232 HTTP/1.1 Conditional Requests June 2014 Copyright Notice Copyright (c) 2014 IETF Trust and the persons identified as the document authors. RFC 7232 HTTP/1.1 Conditional Requests June 2014 Table of Contents 1.
RFC 7232 HTTP/1.1 Conditional Requests June 2014 1. 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. 1.1. 1.2. RFC 7232 HTTP/1.1 Conditional Requests June 2014 repetition). 2. 2.1. Validators come in two flavors: strong or weak. RFC 7231 - Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content. RFC 7230 - Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing.