Skip to content

Document new -SkipHeaderVerification switch on the Invoke-WebRequest and Invoke-RestMethod cmdlets#1387

Merged
juanpablojofre merged 3 commits intoMicrosoftDocs:stagingfrom
dantraMSFT:staging
Jun 22, 2017
Merged

Document new -SkipHeaderVerification switch on the Invoke-WebRequest and Invoke-RestMethod cmdlets#1387
juanpablojofre merged 3 commits intoMicrosoftDocs:stagingfrom
dantraMSFT:staging

Conversation

@dantraMSFT
Copy link
Copy Markdown
Contributor

The fix for issue PowerShell/PowerShell#2895 adds a new switch parameter -SkipHeaderVerification. This switch allows callers to add header values that may not be standards compliant for cases where target sites require them.

All header values are added without validation when this switch is used.

@msftclas
Copy link
Copy Markdown

@dantraMSFT,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@saldana
Copy link
Copy Markdown
Contributor

saldana commented Jun 22, 2017

⚠️ Validation status: warnings

File Status Preview URL Details
reference/6/Microsoft.PowerShell.Utility/Invoke-RestMethod.md ⚠️Warning Details
reference/6/Microsoft.PowerShell.Utility/Invoke-WebRequest.md ⚠️Warning Details

reference/6/Microsoft.PowerShell.Utility/Invoke-RestMethod.md

  • [Warning] Ignore metadata: locale. They are generated by open publish.

reference/6/Microsoft.PowerShell.Utility/Invoke-WebRequest.md

  • [Warning] Ignore metadata: locale. They are generated by open publish.

For more details, please refer to the build report.

Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants