Skip to content

fix: serviceName and portName must correspond to port binding - #1226

Closed
paulish wants to merge 1 commit into
vpulim:masterfrom
paulish:master
Closed

paulish wants to merge 1 commit into
vpulim:masterfrom
paulish:master

Conversation

@paulish

@paulish paulish commented Aug 30, 2023

Copy link
Copy Markdown
Contributor

Soap server code makes an assumption that url may not match the port binding. In this case the first port is used. At the same time WSDL can have multiply services and ports and therefore not only the first port binding should be taken but also first port name and first service name. Without this patch the first port binding is used and the last serviceName and portName. With this patch applied port binding corresponds correct serviceName and portName.

@paulish

paulish commented Aug 30, 2023

Copy link
Copy Markdown
Contributor Author

code-quality tests fails are not related to the changes in code. The first one is IPV6 address against IPV4, others are something with cryptography.

@smokhov

smokhov commented Mar 26, 2025

Copy link
Copy Markdown
Contributor

@w666 -- could you force checks run for this?

@w666

w666 commented Oct 24, 2025

Copy link
Copy Markdown
Collaborator

#1337 adds support for this. It was not a bug, it just was not implemented.
Also, changes in this PR do not fix the problem mentioned in the description. At least it did not work with the tests I created to replicate the issue.

Closing.

@w666
w666 self-requested a review October 24, 2025 19:55
@w666 w666 closed this Oct 24, 2025
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.

3 participants