This test group is documented but not implemented. See developer notes below for details.
This test group tests the following 9 requirement(s).
- "The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 " (rfc2616)
- "An implementation is not compliant if it fails to satisfy one or more
of the MUST or REQUIRED level requirements for the protocols it
- "An implementation that satisfies all the MUST or REQUIRED
level and all the SHOULD level requirements for its protocols is said
to be "unconditionally compliant"" (rfc2616)
- "one that satisfies all the MUST
level requirements but not all the SHOULD level requirements for its
protocols is said to be "conditionally compliant" (rfc2616)
- "An application that sends a request or response message that includes
HTTP-Version of "HTTP/1.1" MUST be at least conditionally compliant
with this specification" (rfc2616)
- "Applications that are at least conditionally
compliant with this specification SHOULD use an HTTP-Version of
"HTTP/1.1" in their messages, and MUST do so for any message that is
not compatible with HTTP/1.0" (rfc2616)
- "some might be REQUIRED by
portions of this specification" (rfc2616)
- "Other hop-by-hop headers MUST be listed in a Connection header,
(section 14.10) to be introduced into HTTP/1.1 (or later)" (rfc2616)
- "And thanks go particularly to Jeff
Mogul and Scott Lawrence for performing the "MUST/MAY/SHOULD" audit" (rfc2616)
These RFC excerpts are not implementation requirements.
They may be used for documentation purposes but do not need to
This test group contains no members.
This test group belongs to no groups.
This test group identifier is test_group/any/requirement-not. Please use that identifier when refering to this test group.