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

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

…ve been added to the "Permanent Message Header Field Names" registry defined in RFC3864 ] ( ). Header field name: Prefer Applicable Protocol: HTTP Status: Standard Author: James M Snell <jasnell@gmail.com> Change controller: IETF Specification document: this specification, Sectio…

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

…der listed below, to be added to the permanent HTTP header registry defined in [RFC3864] Klyne, G., Nottingham, M., and J. Mogul, “Registration Procedures for Message Header Fields,” September 2004. TOC 9.1.1. DASL Header field name: DASL Applicable protocol: http Status: standar…

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

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

… in registry as outlined in Registration Procedures for Message Header Fields [ RFC3864 Ross & Gondrom Expires April 26, 2013 [Page 6] Internet-Draft X-Frame-Options October 2012 4.1 . Registration Template PERMANENT MESSAGE HEADER FIELD REGISTRATION TEMPLATE: Header field name: …

… ], a new message header that conforms to the registry mechanism described in [ RFC3864 ], and two new link relations that conform to the registry mechanism described in [ RFC4287 ]. 16.1 . Content-Type Registration for 'application/atomcat+xml' An Atom Publishing Protocol Catego…

… ], a new message header that conforms to the registry mechanism described in [ RFC3864 ], and two new link relations that conform to the registry mechanism described in [ RFC4287 ]. 16.1 . Content-Type Registration for 'application/atomcat+xml' An Atom Publishing Protocol Catego…

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

… in registry as outlined in Registration Procedures for Message Header Fields [ RFC3864 Ross & Gondrom Expires January 7, 2013 [Page 6] Internet-Draft Frame-Options July 2012 4.1 . Registration Template PERMANENT MESSAGE HEADER FIELD REGISTRATION TEMPLATE: Header field name: Fram…

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

…he Accept-Patch response header has been added to the permanent registry (see [ RFC3864 ]). Header field name: Accept-Patch Applicable Protocol: HTTP Author/Change controller: IETF Specification document: this specification . Security Considerations The security considerations fo…

…specification updates the "Message Headers" registry entry for "Link" in HTTP [ RFC3864 ] to refer to this document. Header Field Name: Link Protocol: http Status: standard Reference: RFC 8288 4.2 . Link Relation Type Registry This specification updates the registration procedure…