2. Requirements Language

Questa sezione conserva il testo RFC per optimistic HTTP/1.1 protocol transitions, inclusi request smuggling risks, parser exploit risks, existing Upgrade tokens, HTTP CONNECT requirements e IANA status.

2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.