From 4ed26484eef998d6e67d73cf8e0a3737007169ee Mon Sep 17 00:00:00 2001 From: Moonchild Date: Sun, 25 Dec 2022 11:42:42 +0000 Subject: Issue #2070 - When multiple HSTS headers are received, only consider the first. This implements a plain interpretations of RFC 6797, which says to only consider the first HSTS header. This slightly conflicts with RFC 7230, which says that sending multiple headers which can't be merged is illegal (except for a specific whitelist which HSTS isn't in), so this situation should never occur in the first place (and would therefore not need the explicit entry in RFC 6797). It improves HSTS robustness dealing with non-compliant servers. Resolves #2070 --- netwerk/protocol/http/nsHttpAtomList.h | 1 + 1 file changed, 1 insertion(+) (limited to 'netwerk/protocol/http/nsHttpAtomList.h') diff --git a/netwerk/protocol/http/nsHttpAtomList.h b/netwerk/protocol/http/nsHttpAtomList.h index e4b22e8da3..c8a01f9ccb 100644 --- a/netwerk/protocol/http/nsHttpAtomList.h +++ b/netwerk/protocol/http/nsHttpAtomList.h @@ -79,6 +79,7 @@ HTTP_ATOM(Service_Worker_Allowed, "Service-Worker-Allowed") HTTP_ATOM(Set_Cookie, "Set-Cookie") HTTP_ATOM(Set_Cookie2, "Set-Cookie2") HTTP_ATOM(Status_URI, "Status-URI") +HTTP_ATOM(Strict_Transport_Security, "Strict-Transport-Security") HTTP_ATOM(TE, "TE") HTTP_ATOM(Title, "Title") HTTP_ATOM(Timeout, "Timeout") -- cgit v1.2.3