WIP: fix Content-Length & Content-Encoding if http response is decompresse…

[kekaifun]

…d by k6

fix #3373

What?

• k6 will decompress http response body if content-encoding is supported, but Content-Length & Content-Encoding is not changed.
• if http resonse header content-encoding has multivalues (aka: response body is compressed with multi different algorithms), if there is a content-encoding we don't support. k6 just skip the not support part and continue to decompress. that will lead errors

Why?

• if response body is decompressed, we should set the content-length & content-header right accordingly
• we need to stop decompress if there is a content-encoding not support instead of skip it and continue to decompress which lead to errors. So users may decompress the response body by themself.

Checklist

• [x ] I have performed a self-review of my code.
• I have added tests for my changes.
• [ x] I have run linter locally (make ci-like-lint) and all checks pass.
• [ x] I have run tests locally (make tests) and all tests pass.
• [ x] I have commented on my code, particularly in hard-to-understand areas.

Related PR(s)/Issue(s)

#3373

[CLAassistant]

All committers have signed the CLA.

[oleiade]

Thanks a lot for your contribution @kekaifun, much appreciated 🙇🏻

As detailled in #3374 we will, however, not be moving forward with merging this, as this would be a breaking change. We will however keep it in mind as we work towards shipping a new HTTP module 🤝