Open jcchavezs opened 6 years ago
usually we do tolerant read and restart if incompatible.
Ex. 'a' is OK, but 'g' is not. We are tolerant reading mixed lengths ex 1, 17 or 31 hex trace ID is fine, but 33 length trace ID or 17 length span Id is invalid, so restart trace and ignore other headers when malformed.
ATM we are not validating the traceID neither the spanID making it possible to receive
a
orabc
. I believe it is worth to validate it like in otherzipkin
implementations.We have two options:
traceId
creation.traceId
andspanId
when they come from upstream.Ping @eirslett @adriancole