Re: [Json] Go JSON parser ignores the case of member names

[Anders Rundgren <[e-mail]>]

On 2016-03-09 22:38, John Cowan wrote:
> Rob Sayre scripsit:
>
>> Well, there are ways to avoid it too (see below). I see it more as an
>> object-mapper convenience than a JSON conformance problem. I imagine object
>> mapping libraries in other languages have this feature too.
>
> The problem arises in cases like this: Suppose the spec says that key
> "alg" specifies the name of the algorithm, and defaults to "none" if
> there is no key.  Then if the upstream provider sends {"typ" : "JWS",
> "ALG": "HS256"}, then a receiver written in Go will see the algorithm
> as HS256,

Which indeed is bad.

> whereas any other receiver will see the algorithm as "none".
> That's almost certainly not the desired result.

Using a RealJSONParser(tm) other receivers will rather choke on the message
and complain about an unexpected "ALG" property.

I'm just in the process adding such a facility to node.js:
https://github.com/cyberphone/node-webpki.org/blob/master/lib/jsonutil.js


Anders