Test-Proxy GZip Hotfix

[scbedd]

@JoshLove-msft went out of his way to contribute a bugfix via #4165

However, given the fact that this probably breaks recordings where gzip is present...we'll need to re-record tests. We will do that in each corresponding auto-created branch from this PR.

• eng/common test branch created
• update test recordings (this bug caused users to disable body matching, accidentally not breaking :P )
• once green is had on all the repos, merge the PRs

[azure-sdk]

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

[scbedd]

@JoshLove-msft I actually think that we lucked out in how this bug broke people. We were doing things straight up wrong, and as a result I believe folks just disabled body matching where they hit this issue. I think that was literally everyone because I have an eng/common update build against core here and it's green (except for something that I believe is unrelated). Notice the failure in group0 existed before I updated the actual version of the test-proxy in package props.

I've run a ton of other builds as well and they're all green except for JS test-utils. I'm going to get the js-tests green and then just merge the eng/common PRs across the board.

Do you have an opposition to that plan?

[JoshLove-msft]

@JoshLove-msft I actually think that we lucked out in how this bug broke people. We were doing things straight up wrong, and as a result I believe folks just disabled body matching where they hit this issue. I think that was literally everyone because I have an eng/common update build against core here and it's green (except for something that I believe is unrelated). Notice the failure in group0 existed before I updated the actual version of the test-proxy in package props.

I've run a ton of other builds as well and they're all green except for JS test-utils. I'm going to get the js-tests green and then just merge the eng/common PRs across the board.

Do you have an opposition to that plan?

Sounds good - we used the same strategy of disabling body matching in .NET. /cc @nisha-bhatia

[azure-sdk]

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

[scbedd]

/check-enforcer override