Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix decompression in web cmdlets #17955

Merged
merged 8 commits into from
Oct 4, 2022

Conversation

iSazonov
Copy link
Collaborator

@iSazonov iSazonov commented Aug 24, 2022

PR Summary

Follow doesn't work for original cmdlet:

Invoke-WebRequest https://httpbin.org/deflate

I don't know why our tests are passed.

I guess there was something changed .Net from early versions.

The fix removes old workaround and turn on embedded automatic decompression in HttpClient handler.

PR Context

PR Checklist

@iSazonov iSazonov added the CL-General Indicates that a PR should be marked as a general cmdlet change in the Change Log label Aug 24, 2022

# Validate response content
$headers.'Content-Encoding'[0] | Should -BeExactly $dataEncoding
# If Content is compressed we cannot read it as JSON.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand this comment. Do we need to convert content from json similar to above at line 601?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this comment is saying that if the content wasn't decompressed correctly then it wouldn't be valid JSON so the test would fail? If that is case, perhaps the comment should make that more clear.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@SteveL-MSFT What about:

Suggested change
# If Content is compressed we cannot read it as JSON.
# If Content is still compressed we cannot read it as JSON.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The thing is, there is no convertto-json call following this comment, so the comment doesn't seem to make sense.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment updated.

@ghost ghost added the Waiting on Author The PR was reviewed and requires changes or comments from the author before being accept label Aug 24, 2022
@PaulHigin
Copy link
Contributor

PaulHigin commented Aug 24, 2022

@iSazonov

Overall, these changes look Ok to me. But I don't know what prompted this PR. Did the tests begin failing at some point? Or is this just code clean up to remove the current workaround and instead use the built-in automatic decompression setting?

@iSazonov
Copy link
Collaborator Author

iSazonov commented Aug 24, 2022

@PaulHigin The Invoke-WebRequest https://httpbin.org/deflate did not work before the PR but our tests for deflate was passed.
And yes, .Net Runtime remove encoding headers after automatic decompression. I was wonder but it makes sense - if there was follow processing it shouldn't see any compression header since content is already not compressed.
I checked this with Wireshark:

  1. Request
    image

  2. Response
    image

Then the cmdlets return the response without Content-Encoding: deflate.


Second issue was with tests. I tried to keep them as near to original as possible. But I started to check with httpbin.org. The site send another response than our WebListener. httpbin.org response has a flag for used decompression method, WebListener haven't. I don't know how enhance WebListener. So I had to change tests.


I don't know why our tests passed before the PR for deflate. I did not investigate either a root is in WebListener or in old workaround.

@ghost ghost removed the Waiting on Author The PR was reviewed and requires changes or comments from the author before being accept label Aug 24, 2022
@ghost ghost added the Review - Needed The PR is being reviewed label Sep 6, 2022
@ghost
Copy link

ghost commented Sep 6, 2022

This pull request has been automatically marked as Review Needed because it has been there has not been any activity for 7 days.
Maintainer, please provide feedback and/or mark it as Waiting on Author

@ghost ghost removed the Review - Needed The PR is being reviewed label Sep 7, 2022
@ghost ghost added the Review - Needed The PR is being reviewed label Sep 14, 2022
@ghost
Copy link

ghost commented Sep 14, 2022

This pull request has been automatically marked as Review Needed because it has been there has not been any activity for 7 days.
Maintainer, please provide feedback and/or mark it as Waiting on Author


# Validate response content
$headers.'Content-Encoding'[0] | Should -BeExactly $dataEncoding
# If Content is compressed we cannot read it as JSON.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The thing is, there is no convertto-json call following this comment, so the comment doesn't seem to make sense.

@ghost ghost added Waiting on Author The PR was reviewed and requires changes or comments from the author before being accept and removed Review - Needed The PR is being reviewed Waiting on Author The PR was reviewed and requires changes or comments from the author before being accept labels Sep 26, 2022
Copy link
Member

@daxian-dbw daxian-dbw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, with one suggestion.

…s.Tests.ps1

Co-authored-by: Dongbo Wang <dongbow@microsoft.com>
@pull-request-quantifier-deprecated

This PR has 22 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

Label      : Extra Small
Size       : +8 -14
Percentile : 8.8%

Total files changed: 3

Change summary by file extension:
.cs : +1 -7
.ps1 : +7 -7

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.


Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

@daxian-dbw
Copy link
Member

@PaulHigin Can you please take another look?

@CarloToso
Copy link
Contributor

CarloToso commented Oct 4, 2022

This PR also fixes
Invoke-WebRequest https://httpbin.org/brotli

@daxian-dbw daxian-dbw assigned daxian-dbw and unassigned PaulHigin Oct 4, 2022
@daxian-dbw daxian-dbw merged commit 3a506b9 into PowerShell:master Oct 4, 2022
@iSazonov iSazonov deleted the web--stream-deflate branch October 4, 2022 17:11
@God-damnit-all
Copy link
Contributor

Is this going to make it into 7.4?

@iSazonov
Copy link
Collaborator Author

It is already in v7.4.0-preview.1

@God-damnit-all
Copy link
Contributor

It is already in v7.4.0-preview.1

Oh, cool. Normally a bot responds to the PR saying if it made it in or whatever.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CL-General Indicates that a PR should be marked as a general cmdlet change in the Change Log Extra Small
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants