# How Is Server-Timing used on the web?

**URL:** <https://discuss.httparchive.org/t/how-is-server-timing-used-on-the-web/1034>\
**Category:** Analysis\
**Created:** [July 27, 2017, 9:26pm UTC](https://discuss.httparchive.org/t/how-is-server-timing-used-on-the-web/1034 "2017-07-27T21:26:33Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![rviscomi](https://yyz1.discourse-cdn.com/flex035/user_avatar/discuss.httparchive.org/rviscomi/32/835_2.png) [@rviscomi](https://discuss.httparchive.org/u/rviscomi)\
**Post date:** [August 3, 2017, 6:29pm UTC](https://discuss.httparchive.org/t/how-is-server-timing-used-on-the-web/1034/16 "2017-08-03T18:29:42Z")

</div>

The issue is that we’re double JSON parsing the payload in the query. The etag value started correctly encoded as `\"foo\"` but after the first parse it became `"foo"` and failed on the second parse.

Rather than using JSON\_EXTRACT to narrow down the payload to an array and a UDF to parse the array, we should just pass the entire payload to the UDF and do all of the parsing there.

 ![image](https://canada1.discourse-cdn.com/flex035/uploads/httparchive/original/1X/dae0db5ef3f781bafcacdda84a37d86c9eb60f54.png)

---

_[View the full topic](https://discuss.httparchive.org/t/how-is-server-timing-used-on-the-web/1034)._