RFC 2068:Hypertext Transfer Protocol -- HTTP/1.1
RFC-Ref

case-insensitive


Click on the red underlined text to get to the source

... Quotation marks surround literal text. Unless stated otherwise, the text is case-insensitive. rule1 | rule2 ...


... o Comparisons of host names MUST be case-insensitive; o Comparisons of scheme names MUST be case-insensitive ...
... case-insensitive; o Comparisons of scheme names MUST be case-insensitive; o An empty abs_path is equivalent to an abs_path of "/". ...
... HTTP character sets are identified by case-insensitive tokens. The complete set of tokens ...
... token All content-coding values are case-insensitive. HTTP/1.1 uses content-coding values in the Accept-Encoding ...
... token All transfer-coding values are case-insensitive. HTTP/1.1 uses transfer coding values in the Transfer-Encoding ...


... header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive. The field value may be preceded by any amount of LWS, though a single SP is preferred. Header fields ...


... client to provide authentication information. It uses an extensible, case-insensitive token to identify the authentication scheme, ...
... realm-value = quoted-string The realm attribute (case-insensitive) is required for all authentication schemes which issue a challenge. The realm value ...


... request-header fields defined by this specification. Field names are case-insensitive. ...


... DIGIT | "." | "-" ) Relationship values are case-insensitive and MAY be extended within the constraints of the sgml-name syntax. The title parameter MAY be ...



Google
Web
RFC-Ref