…r 2011 . IANA Considerations The permanent message header field registry (see [ RFC3864 ]) has been updated with the following registration: Header field name: Origin Applicable protocol: http Status: standard Author/Change controller: IETF Specification document: this specificat…

… The Accept-Post response header must be added to the permanent registry (see [ RFC3864 ]). Header field name: Accept-Post Applicable Protocol: HTTP Author/Change controller: W3C Specification document: this specification 7.2 Preferences on the Prefer Request Header 7.2.1 Summary…

…sage header field registry should be updated with the following registrations: [RFC3864] 11.1. Content-Security-Policy Header field name Content-Security-Policy Applicable protocol http Status standard Author/Change controller W3C Specification document This specification (See Co…

…nt Message Header Field registry, in accordance with the procedures set out in [RFC3864]. Header field name: Downgraded-Mail-From Applicable protocol: mail Status: experimental Author/change controller: IETF Specification document(s): This document (Section 3) Header field name: …

…ith the following header fields, in accordance with the procedures set out in [ RFC3864 ]. Header field name: Date Applicable protocol: Mail Status: standard Author/Change controller: IETF Specification document(s): This document ( section 3.6.1 Resnick Standards Track [Page 39] …

…w provisional registration: see URI Schemes [ RFC7595 ] and Email Header Fields RFC3864 ]. Registrations that are designated as provisional are usually defined as being more readily created, changed, reassigned, moved to another status, or removed entirely. URI Schemes, for examp…

…e" registry as outlined in "Registration Procedures for Message Header Fields" [RFC3864]. 3.1. Registration Template Permanent Message Header Field Names Template: Header field name: X-Frame-Options Applicable protocol: http [RFC2616] Status: Informational Author/change controlle…

…inition Mechanisms", BCP 66 RFC 3406 , DOI 10.17487/RFC3406, October 2002, < >. RFC3864 ] Klyne, G., Nottingham, M., and J. Mogul, "Registration Procedures for Message Header Fields", BCP 90 RFC 3864 DOI 10.17487/RFC3864, September 2004, >. RFC3987 ] Duerst, M. and M. Suignard, "…

…fferent applications. Procedures for registering header fields are defined in [ RFC3864 ]. An extensive set of existing header field registrations is provided in [ RFC4021 ]. One danger of placing additional information in header fields is that Gateways often alter or delete them…

…A has registered the Body header field in the Message Header Fields Registry ([ RFC3864 ]) as follows: Header field name: Body Applicable protocol: None. This registration is made to assure that this header field name is not used at all, in order to not create any problems for 'm…

…with the following header fields, in accordance with the procedures set out in [RFC3864]. Header field name: Date Applicable protocol: Mail Status: standard Author/Change controller: IETF Specification document(s): This document (section 3.6.1) Resnick Standards Track [Page 39] R…

…s Authority (IANA) Permanent Message Header Field registration information per [RFC3864]. Header field name: Strict-Transport-Security Applicable protocol: http Status: standard Author/Change controller: IETF Specification document(s): this one 16. References 16.1. Normative Refe…

… Authority (IANA) Permanent Message Header Field registration information per [ RFC3864 ]. Header field name: Strict-Transport-Security Applicable protocol: http Status: standard Author/Change controller: IETF Specification document(s): this one 16 . References 16.1 . Normative R…

… Authority (IANA) Permanent Message Header Field registration information per [ RFC3864 ]. Header field name: Strict-Transport-Security Applicable protocol: http Status: standard Author/Change controller: IETF Specification document(s): this one 16 . References 16.1 . Normative R…

… been added to the "Permanent Message Header Field Names" registry defined in [ RFC3864 ]. Header field: Forwarded Applicable protocol: http Status: standard Author/Change controller: IETF (iesg@ietf.org) Internet Engineering Task Force Specification document(s): this specificati…