Ned Andreev

A lot of these changes were done in https://github.com/grafana/k6/pull/2426 and already merged. A rough version of the remainder are implemented in https://github.com/grafana/k6/pull/2438, so they need to be split into a...

Since you linked https://github.com/grafana/k6/issues/970, was the HTTP2 server you tried to connect to also h2c (unencrypted)?

Can you elaborate a bit more about what exactly your use case is? You want to serialize protobuf data with k6, but send it as the body of a normal...

Please do not leave "+1" comments, just add a :+1: to the [original post](https://github.com/grafana/k6/issues/2125#issue-983492515). That way we won't have spam in the issues and they can be [sorted by the...

Thanks for opening this issue! This is a simpler code snippet to demonstrate it: ```js import http from 'k6/http'; export default function () { let resp = http.get('https://httpbin.test.k6.io/anything', { headers:...

Thanks for opening this issue! Indeed, the [Encoding API](https://developer.mozilla.org/en-US/docs/Web/API/Encoding_API) seems like a useful one to have in k6. Though it is a Web API, not an ECMAScript one, so I...

Thanks for opening this issue. Unfortunately, we can't make this change in the current `k6/http` API, since it will be a pretty major breaking change. Existing load tests will start...

:man_facepalming: both me and @mstoykov thought you were talking about the `compression` option in https://k6.io/docs/javascript-api/k6-http/params/ (and the `Content-Encoding` request header) :sweat_smile:

Yeah, to get back on topic, adding `Accept-Encoding` by default will be much less of a problem than `Content-Encoding`... :thinking: And a lot of HTTP clients (browsers especially) add it...

Something like this would have to wait for #1007, but it shouldn't be too difficult...