Hello, Hong-- Fiddler shows all of the Set-Cookie
response headers and Cookie
In general, Chrome itself does not send any sort of "deviceID" to the server, but Chrome does expose certain APIs that would allow a script on a page to get a device ID (e.g. for a Digital Rights Management purpose) and that script could conceivably send that ID to the server using a cookie or via another mechanism (e.g. the body of a form POST).
In order to get more specific, you'd need to explain exactly where (e.g. what URL) you think a deviceID is getting sent to a server using a cookie and we could look at that cookie and try to figure out how the deviceID is encoded in that cookie. But it could well be encoded, hashed, encrypted, etc...
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items