… access ought to respond with the 403 (Forbidden) status code Section 6.5.3 of [RFC7231] ). HTTP does not restrict applications to this simple challenge-response framework for access authentication. Additional mechanisms can be used, such as authentication at the transport level …

…ndwidth. This memo defines a status code for sending an informational response [RFC7231], Section 6.2 ) that contains header fields that are likely to be included in the final response. A server can send the informational response containing some of the header fields to help the …

…ndwidth. This memo defines a status code for sending an informational response [RFC7231], Section 6.2 ) that contains header fields that are likely to be included in the final response. A server can send the informational response containing some of the header fields to help the …

…ndwidth. This memo defines a status code for sending an informational response [RFC7231], Section 6.2 ) that contains header fields that are likely to be included in the final response. A server can send the informational response containing some of the header fields to help the …

… as a DID subject identified by a DID . representation As defined for HTTP by [ RFC7231 ]: "information that is intended to reflect a past, current, or desired state of a given resource, in a format that can be readily communicated via the protocol, and that consists of a set of …

… DOI 10.17487/RFC6973, July 2013, < http://www.rfc-editor.org/info/rfc6973 >. [ RFC7231 ] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content", RFC 7231 , DOI 10.17487/RFC7231, June 2014, < http://www.rfc-editor.org/info/rfc7231 >…

…ile URL according to [ URL ]. Clients MAY initially make an HTTP HEAD request [ RFC7231 ] to follow redirects and check for the Link header before making a GET request. 4.1.1 Redirect Examples 4.1.1.1 http to https In this example, the user enters example.com in the sign-in form,…

…derations for Internet Protocols", RFC 6973 DOI 10.17487/RFC6973, July 2013, >. RFC7231 ] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content", RFC 7231 DOI 10.17487/RFC7231, June 2014, >. Reschke Standards Track [Page 11] RFC 761…

…Using a Proxy Clients using a domain-oriented transport proxy like HTTP CONNECT RFC7231 ], Section 4.3.6 ) or SOCKS5 RFC1928 have the option of using named destinations, in which case the client does not perform any A or AAAA queries for destination domains. If the client is conf…

…下 id 可以 省略）。 type 对象的类型。 3.2 检索对象 可以针对对象的 id 属性使用 HTTP GET 方法以检索活动。 服务器 可以 按照 [ RFC7231 ] 中的定义使用HTTP内容协商机制 来选择响应请求时返回的数据类型， 必须 在响应 application/ld+json; profile="https://www.w3.org/ns/activitystreams" 时给出ActivityStreams对象表示格式， 应当 在响应 application/activity+json 时也给出ActivityStreams表示…

… 9.5.1.2. Usage Over HTTP When used for hypermedia systems over a network, HTTP RFC7231 is frequently the protocol of choice for distributing schemas. Misbehaving clients can pose problems for server maintainers if they pull a schema over the network more frequently than necessar…

…, it is returned as either form-encoded or JSON, depending on the HTTP Accept [ RFC7231 ] header. 2.2 Reserved Properties A few POST body property names are reserved when requests are sent as x-www-form-urlencoded or multipart form data. access_token - the OAuth Bearer token auth…

…NOT be sent in the trailer of a chunked-encoded response. If a "100 (Continue)" RFC7231 ] response is sent from the server, the Authentication-Info header SHOULD be included in that response instead of the final response. . Authentication Realms In this protocol, an authenticatio…

… be appended to the well-known URI, or protocol- specific details (e.g., HTTP [ RFC7231 ] method handling). Note that this specification defines neither how to determine the hostname to use to find the well-known URI for a particular application, nor the scope of the metadata dis…

…P/1.1 Message Syntax and Routing [*] RFC7230 B.2 HTTP/1.1 Semantics and Content RFC7231 B.3 HTTP/1.1 Conditional Requests RFC7232 B.4 HTTP/1.1 Range Requests RFC7233 B.5 HTTP/1.1 Authentication RFC7235 B.6 HTTP Status Code 308 (Permanent Redirect) RFC7538 B.7 HTTP Authentication-…