On Jan 10, 2015, at 10:52 AM, Andrew Stuart wrote:

The REST API is returning etags as slashed quoted.

Just wondering if this is intentional, does not seem consistent with the behaviour of the other fields returned from the API.

i.e.

"http_etag": "\"d6d174c76c5fbb5f8a69b648ecd3b27b53a5d27e\”",

It's intentional, but I don't remember why. I think I remember reading that the HTTP ETag header (which we actually don't set in the HTTP response, but probably should) is quoted.

Cheers, -Barry