Mihail Stoykov

Without looking into the proposition too much: Given that #1831 will likely have breaking changes for outputs as well I would prefer if we don't break the interface *once* to...

@vanshaj there is no need for you to be assigned on an issue in order to work and make PRs. I am going to assign you this time, but you...

@shekharshukla it will be beneficial if we have a proto file that reproduces this problem and preferably a js script as well. You can for example make a PR ot...

I am for `2.` - documenting it. This has been the behaviour forever. So this will be a breaking change. That plus the fact that `k6/http` is more or less...

I did look around and as far as I can see none of the fetch API, python's requests or golang stdlib automatically compress the body of a request. So I...

~From a quick test k6 does add `Accept-Encoding` with a value of `gzip`~ see https://github.com/grafana/k6/issues/2586#issuecomment-1176069750

apperantly I was fooled by https://github.com/grafana/k6/issues/1042 , and having now checked with the keylogger from #2487 - we definitely do not send `Accept-Encoding` by default :(

Hi @AndiDog , thanks for the feature request :bow:. As I explained in https://github.com/grafana/k6/pull/2391#issuecomment-1046850416 adding more fields to the Response has its downsides. In that particular case it also added...

This seems like a nice small reasonable change @bmteller :tada:. Thanks for reporting it. Do you want to try to make a PR for it?

Hi @tbourrely, nobody has picked it up. If it was done we would've closed the issue ;)