…dentifiers are associated with resources. For example, the "http" URI scheme ([ RFC2616 ]) uses DNS and TCP-based HTTP servers for the purpose of identifier allocation and resolution. As a result, identifiers such as "http://example.com/somepath#someFrag" often take on meaning th…

…2616 defines the Content-Disposition response header field ( Section 19.5.1 of [RFC2616] ) but points out that it is not part of the HTTP/1.1 Standard ( Section 15.5 ): Content-Disposition is not part of the HTTP standard, but since it is widely implemented, we are documenting it…

… 2616 defines the Content-Disposition response header field (Section 19.5.1 of [RFC2616]) but points out that it is not part of the HTTP/1.1 Standard (Section 15.5): Content-Disposition is not part of the HTTP standard, but since it is widely implemented, we are documenting its u…

…C 2616 defines the Content-Disposition response header field Section 19.5.1 of [RFC2616] ) but points out that it is not part of the HTTP/1.1 Standard ( Section 15.5 ): Content-Disposition is not part of the HTTP standard, but since it is widely implemented, we are documenting it…

…s through server-side search. TOC 1.3. This document uses the terms defined in [RFC2616] Fielding, R., Gettys, J., Mogul, J., Nielsen, H., Masinter, L., Leach, P., and T. Berners-Lee, “Hypertext Transfer Protocol -- HTTP/1.1,” June 1999. , in [RFC4918] Dusseault, L., Ed., “HTTP E…

…presentations of a resource. In this case, the HTTP origin server (defined in [ RFC2616 ]) is the agent acting on behalf of the URI owner. Just as a shared vocabulary has tangible value, the ambiguous use of terms imposes a cost in communication. URI ambiguity refers to the use o…

…oxy, and origin server have the same meaning as in the HTTP/1.1 specification ([RFC2616], Section 1.3). The request-host is the name of the host, as known by the user agent, to which the user agent is sending an HTTP request or from which it is receiving an HTTP response (i.e., t…

…............... 10 . Introduction This specification defines the new HTTP/1.1 [ RFC2616 ] method, PATCH, which is used to apply partial modifications to a resource. A new method is necessary to improve interoperability and prevent errors. The PUT method is already defined to over…

…............... 10 . Introduction This specification defines the new HTTP/1.1 [ RFC2616 ] method, PATCH, which is used to apply partial modifications to a resource. A new method is necessary to improve interoperability and prevent errors. The PUT method is already defined to over…

…ticular, the UTF-16 family, UCS-4, and UTF-32 are not allowed (except over HTTP[RFC2616], which uses a MIME-like mechanism). Thus, if an XML document or external parsed entity is encoded in such character encoding schemes, it cannot be labeled as text/xml or text/xml-external-par…

…credentials (access token). This specification is designed for use with HTTP ([ RFC2616 ]). The use of OAuth over any protocol other than HTTP is out of scope. The OAuth 1.0 protocol ([ RFC5849 ]), published as an informational document, was the result of a small ad hoc community…

…sets of content that share certain language attributes. For example, HTTP/1.1 [ RFC2616 ] describes one such mechanism in its discussion of the Accept-Language header ( Section 14.4 ), which is used when selecting content from servers based on the language of that content. It is,…

…credentials (access token). This specification is designed for use with HTTP ([ RFC2616 ]). The use of OAuth over any protocol other than HTTP is out of scope. The OAuth 1.0 protocol ([ RFC5849 ]), published as an informational document, was the result of a small ad hoc community…

…credentials (access token). This specification is designed for use with HTTP ([ RFC2616 ]). The use of OAuth over any protocol other than HTTP is out of scope. The OAuth 1.0 protocol ([ RFC5849 ]), published as an informational document, was the result of a small ad hoc community…

…credentials (access token). This specification is designed for use with HTTP ([ RFC2616 ]). The use of OAuth over any protocol other than HTTP is out of scope. The OAuth 1.0 protocol ([ RFC5849 ]), published as an informational document, was the result of a small ad hoc community…