…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-…

…at the Relying Party uses a "User-Agent" header explained in Section 5.5.3. of [RFC7231] to identify the name and version of the Relying Party software used. It is useful to track capabilities of Relying Parties in the event of changes to the RPKI standards. When the Relying Part…

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

…trailer) fields is an onerous task; even with the guidance in Section 8.3.1 of [RFC7231] , there are many decisions -- and pitfalls -- for a prospective HTTP field author. Once a field is defined, bespoke parsers and serializers often need to be written, because each field value …

…railer) fields is an onerous task; even with the guidance in Section 8.3.1 of [ RFC7231 , there are many decisions -- and pitfalls -- for a prospective HTTP field author. Once a field is defined, bespoke parsers and serializers often need to be written, because each field value h…

….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 Authen…

…erve as 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 …

…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-…

…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…

… that these (and the header field name) are case insensitive. Section 8.3.1 of [RFC7231] calls for documenting the following details for this new header field: o Only one single value is allowed in a Hobareg header field. Should more than one (a list) be encountered, or any other…

…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-…

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

…ent 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. In the event there is no indieauth-metadata URL provided, for compatibility with previous revisions of IndieAut…

…apid". A push service MAY reject a request with a 403 (Forbidden) status code [ RFC7231 ] if the JWT signature or its claims are invalid. A push service MUST NOT use information from an invalid token. The JWT MUST use a JSON Web Signature (JWS) [ RFC7515 ]. The signature MUST use…

… at which time the server might respond with "HTTP Redirection" Section 6.4 of [RFC7231] ), pointing to the URI on the second server. The client will follow the redirection and pass an Authorization header field, including the <opaque> data. Proxies MUST be completely transparent…