DeserializeJSON() does not treat the values "\u000B" and "\u000b" the same. Case sensitivity should not matter according to https://www.ietf.org/rfc/rfc4627.txt:
Any character may be escaped. If the character is in the Basic Multilingual Plane (U+0000 through U+FFFF), then it may be represented as a six-character sequence: a reverse solidus, followed by the lowercase letter u, followed by four hexadecimal digits that encode the character's code point. The hexadecimal letters A though F can be upper or lowercase. So, for example, a string containing only a single reverse solidus character may be represented as "\u005C".
I've added a test case and fix for this ticket & confirmed the issue happened both affected version(18.104.22.168) and the latest version (22.214.171.124-SNAPSHOT) on lucee when test the uppercase using deseralizeJSON function. So, the Lucee result is different compare to ACF.
Pull request: https://github.com/lucee/Lucee/pull/774
Your pull request is currently closed…is that normal? Or does that mean that it won’t eventually get merged in for a future release? Is there anything I can do to help move this along?
Thank you for finding a fix! I was able to apply your changes, but I’d like to get back on a stable release instead of my custom build eventually.