WireMock published in a VM not working with SOAP (Timeout) #372

New Issue

adam · 2025-12-29T15:22:08+01:00

adam commented

2025-12-29 15:22:08 +01:00

Originally created by @devmariodiaz on GitHub (Oct 14, 2021).

Originally assigned to: @StefH on GitHub.

Hello Stef,

Good afternoon Stef,

I hope you are doing well;

I am trying to send the xml-soap body request as a pattern, when I am running in localhost:8080 its working perfectly, after deploying in azure devOps pipeline URL:8080 when the pattern in body request contains "soap:envelope" it is not working, and keep processing (Timeout), could you please let me know if you have any recommendation for this problem, I am publishing in http without SSL

You can see the body pattern as follows:

SOAP request body:

"Body": {
"Matcher": {
"Name": "ExactMatcher",
"Pattern": "<?xml version=\"1.0\" encoding=\"utf-8\"?><soap:Envelope xmlns:xsi=\"http://someurlthatnotexist/XMLSchema-instance\" xmlns:xsd=\"http://someurlthatdosntexist/XMLSchema\" xmlns:soap=\"http://schemas.xmlsoap.org/soap/envelope/\"> xmlns=\"https://www.someurlthatdoesntexist.com/xml/\">13"
}
}
},

And this is the body request:

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://someurlthatdosntexist/XMLSchema" xmlns:xsi="http://someurlthatnotexist/XMLSchema-instance">
   <soap:Body>
      <CtoF xmlns="https://www.someurlthatdoesntexist.com/xml/">
         <C>13</C>
      </CtoF>
   </soap:Body>
</soap:Envelope>

Originally created by @devmariodiaz on GitHub (Oct 14, 2021). Originally assigned to: @StefH on GitHub. Hello Stef, Good afternoon Stef, I hope you are doing well; I am trying to send the xml-soap body request as a pattern, when I am running in localhost:8080 its working perfectly, after deploying in azure devOps pipeline URL:8080 when the pattern in body request contains "<soap:envelope>" it is not working, and keep processing (Timeout), could you please let me know if you have any recommendation for this problem, I am publishing in http without SSL You can see the body pattern as follows: SOAP request body: ``` "Body": { "Matcher": { "Name": "ExactMatcher", "Pattern": "<?xml version=\"1.0\" encoding=\"utf-8\"?><soap:Envelope xmlns:xsi=\"http://someurlthatnotexist/XMLSchema-instance\" xmlns:xsd=\"http://someurlthatdosntexist/XMLSchema\" xmlns:soap=\"http://schemas.xmlsoap.org/soap/envelope/\"> xmlns=\"https://www.someurlthatdoesntexist.com/xml/\">13" } } }, ``` And this is the body request: ``` <?xml version="1.0" encoding="UTF-8"?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://someurlthatdosntexist/XMLSchema" xmlns:xsi="http://someurlthatnotexist/XMLSchema-instance"> <soap:Body> <CtoF xmlns="https://www.someurlthatdoesntexist.com/xml/"> <C>13</C> </CtoF> </soap:Body> </soap:Envelope> ```

adam added the question label 2025-12-29 15:22:08 +01:00

adam closed this issue

2025-12-29 15:22:09 +01:00

adam commented

2025-12-29 15:22:10 +01:00

@StefH commented on GitHub (Oct 15, 2021):

Hello Mario,

It could be related to using 8080, did you also try to use 443 (https?)

And for an example see this:
https://github.com/WireMock-Net/WireMock.Net/tree/master/examples/WireMock.Net.WebApplication.NETCore3

And maybe this link can help:

@StefH commented on GitHub (Oct 15, 2021): Hello Mario, It could be related to using 8080, did you also try to use 443 (https?) And for an example see this: https://github.com/WireMock-Net/WireMock.Net/tree/master/examples/WireMock.Net.WebApplication.NETCore3 And maybe this link can help: - https://github.com/WireMock-Net/WireMock.Net/wiki/WireMock-as-a-%28Azure%29-Web-App - https://github.com/WireMock-Net/WireMock.Net/wiki/Using-HTTPS-%28SSL%29

adam commented

2025-12-29 15:22:10 +01:00

@StefH commented on GitHub (Jan 6, 2022):

Hello @devmariodiaz,

Did you have time time to check this issue ?

@StefH commented on GitHub (Jan 6, 2022): Hello @devmariodiaz, Did you have time time to check this issue ?

adam commented

2025-12-29 15:22:11 +01:00

@StefH commented on GitHub (Feb 20, 2022):

Hello @devmariodiaz

Did you find a solution for this?

@StefH commented on GitHub (Feb 20, 2022): Hello @devmariodiaz Did you find a solution for this?

adam commented

2025-12-29 15:22:11 +01:00

@StefH commented on GitHub (May 3, 2022):

Hello @devmariodiaz, is this still a problem for you? Else I'll close this issue.

@StefH commented on GitHub (May 3, 2022): Hello @devmariodiaz, is this still a problem for you? Else I'll close this issue.

adam commented

2025-12-29 15:22:11 +01:00

@devmariodiaz commented on GitHub (May 3, 2022):

Hello Stef, I'll close this issue because this is already solved.

Thanks for all 💯

@devmariodiaz commented on GitHub (May 3, 2022): Hello Stef, I'll close this issue because this is already solved. Thanks for all 💯

Sign in to join this conversation.

Branches Tags

master

mime-part-matcher

version-2.x

MappingSerializer

1341-mapping-json

stef-aspire-tests-updates

bug/973-TinyMapper

bug/1149-AppendGuidToSavedMappingFile

feature/1150-DockerImageVersion

61

stef-1108

stef-1097

stef-1083-MessageOptions_Type_Conflict

stef-1062-logger

stef-IgnoreOpenApiErrors

stef-928-TypeLoadException-FluentAssertions-net472

nunit

stef-849

stef-847-regex-questionmark

http_verb

WireMockServerContext

webapp

ai

CommandLineArgumentsParser

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/WireMock.Net-wiremock#372