Try to make error messages useful when using SOAP 1.2 #1228
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
fixed typos in SOAP 1.2 error test cases.
fixed typos in SOAP 1.2 error test cases.
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.
When using SOAP 1.2 the Fault error messages were
Uncaught Error: undefined: undefined.They are now of the form
Uncaught Error: s:Sender: w:InternalError: The WS-Management service cannot process the request because the XML is invalid.: {"FaultDetail":"http://schemas.dmtf.org/wbem/wsman/1/wsman/faultDetail/Invalid","WSManFault":{"attributes":{"Code":"2150858819","Machine":"dell"},"Message":"WinRM cannot process the request because the input XML uses an undefined XML namespace."}}, while verbose, it's actually useful.