They duplicate the rawOuput field and essentially double the size of HTTP measurements, which creates problems both for us and the clients. A typical GET measurement with 500 probes is about 13 MB of JSON and can exceed 20 MB depending on the headers. We already provide a separate headers field with the parsed values, and for the rare use of the raw text, it can be parsed trivially from rawBody since the HTTP response structure is very simple.
The fields should be completely removed, possibly with some other changes, in a v2 response schema.
They duplicate the
rawOuputfield and essentially double the size of HTTP measurements, which creates problems both for us and the clients. A typical GET measurement with 500 probes is about 13 MB of JSON and can exceed 20 MB depending on the headers. We already provide a separateheadersfield with the parsed values, and for the rare use of the raw text, it can be parsed trivially fromrawBodysince the HTTP response structure is very simple.The fields should be completely removed, possibly with some other changes, in a v2 response schema.