HTTP/2 200 date: Tue, 07 Oct 2025 19:27:08 GMT content-type: text/plain; charset=utf-8 content-length: 268 cf-ray: 98afcb4a1a39d86d-BLR last-modified: Mon, 31 Mar 2025 19:36:32 GMT etag: "1a2-631a889932608-gzip" accept-ranges: bytes vary: Accept-Encoding content-encoding: gzip strict-transport-security: max-age=31536000; includeSubDomains x-frame-options: SAMEORIGIN x-xss-protection: 1; mode=block x-content-type-options: nosniff cf-cache-status: DYNAMIC set-cookie: __cf_bm=oS6HGE8mipuC_pnNxOP4qR3g1pM2eObRaLiFVDOSoBM-1759865228-1.0.1.1-y7VVb32DsvEERJAh9EKpanQs.YUaxLL7tRuFW61GYQryleA5NJSTyPut0YqykFJRxZVCoa6dIGMidSq1d4gkdP1Wf_ZMFR2kmqghGUyDpYA; path=/; expires=Tue, 07-Oct-25 19:57:08 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None server: cloudflare alt-svc: h3=":443"; ma=86400 [BCP90] Best Current Practice 90, . At the time of writing, this BCP comprises the following: Klyne, G., Nottingham, M., and J. Mogul, "Registration Procedures for Message Header Fields", BCP 90, RFC 3864, DOI 10.17487/RFC3864, September 2004, .