support for SOAP 1.2 and broken web-services #134
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
|
@widgetti, thanks for sending this over! I’ll make some time this week to review. Apologies for the delay. |
|
Up. Another russian company need 1.2 version of protocol :) |
|
Any chance to get SOAP 1.2 support merged? |
|
If someone can resolve the conflicts and retest with one of those Russian services, I can commit to a speedy review and merge this week. |
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.
Hello, this is my approach to work with Russian Post company tracking web-service which seems to be autogenerated by Java tooling and cannot understand SOAP envelopes even in 1.1 version that gowsdl produces.
It also has simple implementation for SOAP 1.2 protocol for another Russian post service mainly just used for changed XML namespace names and HTTP headers
Criticism is welcome