Support alternate client object (ServerXMLHTTP) #429
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
added 2 commits
March 19, 2020 15:14
This update adds support to optionally use ServerXMLHTTP in place of the standard WinHttpRequest object for Rest API calls.
If you don't specify the version number, it does not necessarily use the most current version. It may use 3.0 which does not have the same properties and methods and will cause errors.
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.
This update adds support to optionally use ServerXMLHTTP in place of the standard WinHttpRequest object for Rest API calls.
As described more in issue #428, some API endpoints are very specific about the
Content-Typeheader and will fail if the WinHttpRequest appends an encoding string to theContent-Type. Using the ServerXMLHTTP object allows us to bypass the issue and successfully post to the API endpoint without theContent-Typeheader being changed during the call. Closes #428