Use basic parsing to avoid IE dependency - #58
Merged
Derek (derekfreed) merged 1 commit intoFeb 27, 2018
Conversation
| $webResult = Invoke-WebRequest $page | ||
| $prototypeLink = $webResult.Links | Select-Object -ExpandProperty href | Where-Object { | ||
| $webResult = Invoke-WebRequest $page -UseBasicParsing | ||
| $prototypeLink = $webResult.Links | Select-Object -ExpandProperty href -ErrorAction SilentlyContinue | Where-Object { |
Member
Author
There was a problem hiding this comment.
This is required because the new output doesn't always contain an href property, luckily those are links we want to ignore anyways.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I was running into this error:
The response content cannot be parsed because the Internet Explorer engine is not available, or Internet Explorer’s first-launch configuration is not complete.when running under the context of a DSC resource I'm developing that leverages this module. Using the basic parsing resolves that error by avoiding the dependency on IE entirely.