Closed JosefWN closed 2 years ago
According to RFC7252:
All multi-byte integers in this protocol are interpreted in network byte order.
... but it seems GetETag returns a little endian checksum, is this intentional? https://github.com/plgd-dev/go-coap/blob/004711823039d45af60bce6c639835a180f78bdd/message/getETag.go#L42
GetETag
That seems really suspicious indeed.
@jkralik: any reason why this is little endian while everything else is big endian?
Yes this is a bug.
Thanks for the catch @JosefWN !
According to RFC7252:
... but it seems
GetETag
returns a little endian checksum, is this intentional? https://github.com/plgd-dev/go-coap/blob/004711823039d45af60bce6c639835a180f78bdd/message/getETag.go#L42