3 ms·
The answer to that is we should not be using _any_ case-insensitive strings in protocols. They are fine for human-visible names, but field names and internal e
by theamk 7y ago
The answer to that is we should not be using _any_ case-insensitive strings in protocols.
They are fine for human-visible names, but field names and internal enum values should use byte-by-byte comparison. It just makes entire class of vulnerabilities go away.
- deathanatos 7y agoThey are case-sensitive. > The "alg" value is a case-sensitive ASCII string containing a StringOrURI value. This Header Parameter MUST be present and MUST be understood and processed by implementations.
- JdeBP 7y agoBut the protocol says that they are case-insensitive! is not a good response to the assertion that machine-to-machine protocols should not be case-insensitive, which is what theamk said.