…fer Protocol -- HTTP/1.1 ”, RFC 2068, DOI 10.17487/RFC2068 , January 1997, < >. RFC2557 Palme, J., Hopmann, A., and N. Shelness, “ MIME Encapsulation of Aggregate Documents, such as HTML (MHTML) ”, RFC 2557, DOI 10.17487/RFC2557 , March 1999, < >. RFC5322 Resnick, P., Ed., “ Inte…

…E container types (e.g., the message and multipart types) is defined by MHTML [ RFC2557 ]. Protocols that do not use the MIME message header syntax, but that do allow some form of tagged metadata to be included within messages, may define their own syntax for defining a base URI …

…E container types (e.g., the message and multipart types) is defined by MHTML [ RFC2557 ]. Protocols that do not use the MIME message header syntax, but that do allow some form of tagged metadata to be included within messages, may define their own syntax for defining a base URI …

…IME container types (e.g., the message and multipart types) is defined by MHTML RFC2557 ]. Protocols that do not use the MIME message header syntax, but that do allow some form of tagged metadata to be included within messages, may define their own syntax for defining a base URI …

…IME container types (e.g., the message and multipart types) is defined by MHTML RFC2557 ]. Protocols that do not use the MIME message header syntax, but that do allow some form of tagged metadata to be included within messages, may define their own syntax for defining a base URI …

… the header field of the same name defined for MIME body parts in Section 4 of [RFC2557] . However, its appearance in an HTTP message has some special implications for HTTP recipients. If Content-Location is included in a 2xx (Successful) response message and its value refers (af…

… the header field of the same name defined for MIME body parts in Section 4 of [RFC2557] . However, its appearance in an HTTP message has some special implications for HTTP recipients. Fielding & Reschke Standards Track [Page 15] RFC 7231 HTTP/1.1 Semantics and Content June 2014 …

…text Transfer Protocol -- HTTP/1.1" RFC 2068 DOI 10.17487/RFC2068 January 1997 [RFC2557] Palme, J. Hopmann, A. , and N. Shelness "MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)" RFC 2557 DOI 10.17487/RFC2557 March 1999 [RFC5322] Resnick, P., Ed. "Internet Message…

…text Transfer Protocol -- HTTP/1.1" RFC 2068 DOI 10.17487/RFC2068 January 1997 [RFC2557] Palme, J. Hopmann, A. , and N. Shelness "MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)" RFC 2557 DOI 10.17487/RFC2557 March 1999 [RFC5322] Resnick, P., Ed. "Internet Message…

…IME container types (e.g., the message and multipart types) is defined by MHTML RFC2557 ]. Protocols that do not use the MIME message header syntax, but that do allow some form of tagged metadata to be included within messages, may define their own syntax for defining a base URI …

…IME container types (e.g., the message and multipart types) is defined by MHTML RFC2557 ]. Protocols that do not use the MIME message header syntax, but that do allow some form of tagged metadata to be included within messages, may define their own syntax for defining a base URI …

… the header field of the same name defined for MIME body parts in Section 4 of [RFC2557]. However, its appearance in an HTTP message has some special implications for HTTP recipients. Fielding & Reschke Standards Track [Page 15] RFC 7231 HTTP/1.1 Semantics and Content June 2014 I…

…ME container types (e.g., the message and multipart types) is defined by MHTML [RFC2557]. Protocols that do not use the MIME message header syntax, but that do allow some form of tagged metadata to be included within messages, may define their own syntax for defining a base URI a…

…IME container types (e.g., the message and multipart types) is defined by MHTML RFC2557 ]. Protocols that do not use the MIME message header syntax, but that do allow some form of tagged metadata to be included within messages, may define their own syntax for defining a base URI …

… the header field of the same name defined for MIME body parts in Section 4 of [RFC2557] . However, its appearance in an HTTP message has some special implications for HTTP recipients. Fielding & Reschke Standards Track [Page 15] RFC 7231 HTTP/1.1 Semantics and Content June 2014 …