…eader Fields New header fields are registered using the procedures described in RFC3864 ]. The requirements for header field names are defined in Section 4.1 of [RFC3864] . Authors of specifications defining new fields are advised to keep the name as short as practical, and not t…

…NA Considerations 9.1. Cookie The permanent message header field registry (see [RFC3864]) needs to be updated with the following registration: Header field name: Cookie Applicable protocol: http Status: standard Author/Change controller: IETF Specification document: this specific…

…rity (IANA) following the "Registration Procedures for Message Header Fields" [ RFC3864 ]. 4.1 . The Accept-Post Response Header The Accept-Post response header should be added to the permanent registry of message header fields (see [ RFC3864 ]), taking into account the guideline…

…llow one to attack the other. The permanent message header field registry (see [RFC3864] ) should be updated with the following registrations: Header field name: Origin Applicable protocol: http Status: standard Author/Change controller: IETF Specification document: this specific…

…licy Framework (SPF) April 2014 14.2 . The Received-SPF Mail Header Field Per [ RFC3864 ], the "Received-SPF:" header field is added to the IANA "Permanent Message Header Field Names" registry. The following is the registration template: Header field name: Received-SPF Applicable…

…2011 9 . 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…

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

…ons. 9 . IANA Considerations The permanent message header field registry (see [ RFC3864 ]) has been updated with the following registrations. Barth Standards Track [Page 33] RFC 6265 HTTP State Management Mechanism April 2011 9.1 . Cookie Header field name: Cookie Applicable prot…

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

…is specification updates the Message Header registry entry for "Link" in HTTP [ RFC3864 ] to refer to this document. Header field: Link Applicable protocol: http Status: standard Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force Specification document…

…tions. 9. IANA Considerations The permanent message header field registry (see [RFC3864]) has been updated with the following registrations. 9.1. Cookie Header field name: Cookie Applicable protocol: http Status: standard Author/Change controller: IETF Specification document: thi…

…his specification updates the Message Header registry entry for "Link" in HTTP [RFC3864] to refer to this document. Header field: Link Applicable protocol: http Status: standard Author/change controller: IETF (iesg@ietf.org) Internet Engineering Task Force Specification document(…

…tions. . IANA Considerations The permanent message header field registry (see [ RFC3864 ]) has been updated with the following registrations. Barth Standards Track [Page 33] RFC 6265 HTTP State Management Mechanism April 2011 9.1 . Cookie Header field name: Cookie Applicable prot…

…tions. . IANA Considerations The permanent message header field registry (see [ RFC3864 ]) has been updated with the following registrations. Barth Standards Track [Page 33] RFC 6265 HTTP State Management Mechanism April 2011 9.1 . Cookie Header field name: Cookie Applicable prot…

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