Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing

Abstract

The Hypertext Transfer Protocol (HTTP) is a stateless applicationlevel protocol for distributed, collaborative, hypertext information systems. This document provides an overview of HTTP architecture and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) schemes, defines the HTTP/1.1 message syntax and parsing requirements, and describes related security concerns for implementations. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7230.

LoCO: Local Cooperative Data Offloading System Based on Location Information

“…The LoCO system supports uniform resource locator (URL) etc. to specify the data, since it is relied upon to perform the range request function [19] which is a kind of conditional request [20] within HTTP/1.1 [21], [22] to enhance its flexibility and versatility. The function is also usable in the future because it is compatible with HTTP/2.0 [23].…”

“…Next, each terminal cooperatively downloads 10 MB of data via the LoCO system. Note that the data request and download via the Internet was performed based on the range request [20], which is a kind of a conditional request [19] in HTTP/1.1 [21], [22]. We also focused the evaluation on the effect on mobile and fixed networks, and thus we excluded the direct communication traffic from the result describing the total amount of traffic.…”

Loop Detection in Content Delivery Networks (CDNs)

“…HTTP defines the Via header field in Section 5.7.1 of [RFC7230] for "tracking message forwards, avoiding request loops, and identifying the protocol capabilities of senders along the request/response chain. "…”

“…This specification uses the Augmented Backus-Naur Form (ABNF) notation of [RFC5234] with a list extension, defined in Section 7 of [RFC7230], that allows for compact definition of comma-separated lists using a '#' operator (similar to how the '*' operator indicates repetition). Additionally, it uses a token (OWS), uri-host, and port rules from [RFC7230]…”

“…@[] {}". See Section 3.2.6 of [RFC7230]. Likewise, note the rules for when parameter values need to be quoted in Section 3.1.1 of [RFC7231].…”