共找到 150 条与 HTTP 相关的标准，共 10 页
"This document specifies ""Alternative Services"" for HTTP@ which allow an origin??s resources to be authoritatively available at a separate network location@ possibly accessed with a different protocol configuration."
HTTP Alternative Services
This specification allows HTTP CONNECT requests to indicate what protocol is intended to be used within the tunnel once established@ using the ALPN header field.
The ALPN HTTP Header Field
This specification defines an HTTP header field that can be used by a client to request that certain behaviors be employed by a server while processing a request.
Prefer Header for HTTP
The Hypertext Transfer Protocol (HTTP) provides a simple challengeresponse authentication mechanism that may be used by a server to challenge a client request and by a client to provide authentication information. This document defines the HTTP Digest Authentication scheme that can be used with the HTTP authentication mechanism.
HTTP Digest Access Authentication
本文件涵盖了一致性系统使用的通信协议的协议特定部分，作为RESTful HTTP绑定。 本文件的范围（不限于以下内容）： ? 绑定oneM2M协议原语类型到HTTP方法。 ? 绑定oneM2M响应状态码（成功/不成功）到HTTP响应码。 ? 绑定oneM2M RESTful资源到HTTP资源。 本文件依赖于核心协议规范（ETSI TS 118 104 [3]）的数据类型。
oneM2M HTTP Protocol Binding
Several applications extending the Hypertext Transfer Protocol (HTTP) require a feature to do partial resource modification. The existing HTTP PUT method only allows a complete replacement of a document. This proposal adds a new HTTP method@ PATCH@ to modify an existing HTTP resource.
PATCH Method for HTTP
The present document will cover the protocol specific part of communication protocol used by oneM2M compliant systems as RESTful HTTP binding. The scope of the present document is (not limited to as shown below): Binding oneM2M Protocol primitive types to HTTP method. Binding oneM2M response status codes (successful/unsuccessful) to HTTP response codes. Binding oneM2M RESTful resources to HTTP resources. The present document is depending on Core Protocol specification (ETSI TS 118 104 [3]) for data types.
HTTP Protocol Binding (V1.0.0)
This document specifies the ORIGIN frame for HTTP/2@ to indicate what origins are available on a given connection.
The ORIGIN HTTP/2 Frame
HTTP Protocol Binding (V1.0.0)
The immutable HTTP response Cache-Control extension allows servers to identify resources that will not be updated during their freshness lifetime. This ensures that a client never needs to revalidate a cached fresh resource to be certain it has not been modified.
HTTP Immutable Responses
This document specifies Metalink/HTTP: Mirrors and Cryptographic Hashes in HTTP header fields@ a different way to get information that is usually contained in the Metalink XML-based download description format. Metalink/HTTP describes multiple download locations (mirrors)@ Peer-to-Peer@ cryptographic hashes@ digital signatures@ and other information using existing standards for HTTP header fields. Metalink clients can use this information to make file transfers more robust and reliable. Normative requirements for Metalink/HTTP clients and servers are described here.
Metalink/HTTP: Mirrors and Hashes
This document defines an HTTP extension header field that allows proxy components to disclose information lost in the proxying process@ for example@ the originating IP address of a request or IP address of the proxy on the user-agent-facing interface. In a path of proxying components@ this makes it possible to arrange it so that each subsequent component will have access to@ for example@ all IP addresses used in the chain of proxied HTTP requests. This document also specifies guidelines for a proxy administrator to anonymize the origin of a request.
Forwarded HTTP Extension
本文件涵盖了一致性系统使用的通信协议的协议特定部分，作为RESTful HTTP绑定。 本文件的范围包括（但不限于以下内容）： ? 将oneM2M协议原语类型绑定到HTTP方法。 ? 将oneM2M响应状态码（成功/不成功）绑定到HTTP响应码。 ? 将oneM2M RESTful资源绑定到HTTP资源。 本文件依赖于核心协议规范（oneM2M TS-0004）中的数据类型。
HTTP Protocol Binding (oneM2M TS-0009-v1.0.1)
HTTP PROTOCOL BINDING (ONEM2M TS-0009-V1.0.1)
"Introduction This document defines the HTTP Cookie and Set-Cookie header fields. Using the Set-Cookie header field@ an HTTP server can pass name/value pairs and associated metadata (called cookies) to a user agent. When the user agent makes subsequent requests to the server@ the user agent uses the metadata and other information to determine whether to return the name/value pairs in the Cookie header. Although simple on their surface@ cookies have a number of complexities. For example@ the server indicates a scope for each cookie when sending it to the user agent. The scope indicates the maximum amount of time in which the user agent should return the cookie@ the servers to which the user agent should return the cookie@ and the URI schemes for which the cookie is applicable. There are two audiences for this specification: developers of cookie-generating servers and developers of cookie-consuming user agents. To maximize interoperability with user agents@ servers SHOULD limit themselves to the well-behaved profile defined in Section 4 when generating cookies. User agents MUST implement the more liberal processing rules defined in Section 5@ in order to maximize interoperability with existing servers that do not conform to the well-behaved profile defined in Section 4. This document specifies the syntax and semantics of these headers as they are actually used on the Internet. In particular@ this document does not create new syntax or semantics beyond those in use today. The recommendations for cookie generation provided in Section 4 represent a preferred subset of current server behavior@ and even the more liberal cookie processing algorithm provided in Section 5 does not recommend all of the syntactic and semantic variations in use today. Where some existing software differs from the recommended protocol in significant ways@ the document contains a note explaining the difference. Prior to this document@ there were at least three descriptions of cookies: the so-called ""Netscape cookie specification"" [Netscape]@ RFC 2109 [RFC2109]@ and RFC 2965 [RFC2965]. However@ none of these documents describe how the Cookie and Set-Cookie headers are actually used on the Internet (see [Kri2001] for historical context). In relation to previous IETF specifications of HTTP state management mechanisms@ this document requests the following actions: 1. Change the status of [RFC2109] to Historic (it has already been obsoleted by [RFC2965]). 2. Change the status of [RFC2965] to Historic. 3. Indicate that [RFC2965] has been obsoleted by this document. In particular@ in moving RFC 2965 to Historic and obsoleting it@ this document deprecates the use of the Cookie2 and Set-Cookie2 header fields."
HTTP State Management Mechanism
