(GH-11155) Document body-to-query-param encoding #11157
Merged
Conversation
This file contains 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
Prior to this change, the documentation didn't clearly indicate that the converted key-value pairs for requests from the **Body** parameter were URL encoded or point users to how those strings are encoded. This change: - Adds a brief note indicating that the cmdlet uses the `WebUtility.UrlEncode()` method and points to that method reference for more information about the encoding behavior. - Resolves MicrosoftDocs#11155 - Fixes AB#260889
|
Learn Build status updates of commit 59f5456:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| reference/7.2/Microsoft.PowerShell.Utility/Invoke-RestMethod.md | View (powershell-7.2) | Details | |
| reference/7.2/Microsoft.PowerShell.Utility/Invoke-WebRequest.md | View (powershell-7.2) | Details | |
| reference/7.4/Microsoft.PowerShell.Utility/Invoke-RestMethod.md | View (powershell-7.4) | Details | |
| reference/7.4/Microsoft.PowerShell.Utility/Invoke-WebRequest.md | View (powershell-7.4) | Details | |
| reference/7.5/Microsoft.PowerShell.Utility/Invoke-RestMethod.md | View (powershell-7.5) | Details | |
| reference/7.5/Microsoft.PowerShell.Utility/Invoke-WebRequest.md | View (powershell-7.5) | Details |
reference/7.2/Microsoft.PowerShell.Utility/Invoke-RestMethod.md
- Line 0, Column 0: [Warning: xref-not-found - See documentation]
Cross reference not found: 'System.Net.WebUtility.UrlEncode'.
reference/7.2/Microsoft.PowerShell.Utility/Invoke-WebRequest.md
- Line 0, Column 0: [Warning: xref-not-found - See documentation]
Cross reference not found: 'System.Net.WebUtility.UrlEncode'.
reference/7.4/Microsoft.PowerShell.Utility/Invoke-RestMethod.md
- Line 0, Column 0: [Warning: xref-not-found - See documentation]
Cross reference not found: 'System.Net.WebUtility.UrlEncode'.
reference/7.4/Microsoft.PowerShell.Utility/Invoke-WebRequest.md
- Line 0, Column 0: [Warning: xref-not-found - See documentation]
Cross reference not found: 'System.Net.WebUtility.UrlEncode'.
reference/7.5/Microsoft.PowerShell.Utility/Invoke-RestMethod.md
- Line 0, Column 0: [Warning: xref-not-found - See documentation]
Cross reference not found: 'System.Net.WebUtility.UrlEncode'.
reference/7.5/Microsoft.PowerShell.Utility/Invoke-WebRequest.md
- Line 0, Column 0: [Warning: xref-not-found - See documentation]
Cross reference not found: 'System.Net.WebUtility.UrlEncode'.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
sdwheeler
approved these changes
Jun 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Summary
Prior to this change, the documentation didn't clearly indicate that the converted key-value pairs for requests from the Body parameter were URL encoded or point users to how those strings are encoded.
This change:
WebUtility.UrlEncode()method and points to that method reference for more information about the encoding behavior.PR Checklist