SOAP request 500 error - AddressFilter mismatch at the EndpointDispatcher

Ask the Experts and Postman Tips
,
1

Hello,

I’ve been searching through the help topics for this error I’ve been receiving through Postman but haven’t found any topics regarding AddressFilter mismatch. I’ve been able to get this SOAP post to work via the application SOAPUI where i was receiving this samem exact addressFilter mismatch error. I was able to resolve the issue by Enabling WS-A addresssing and check marking the Add default wsa:TO: which allowed a successfull 200 reponse. I’m trying to track down any information with Postman and WS-Addressing to enable this same type option. If any more information is needed please let me know.

500Internal Server Error

“http://www.w3.org/2005/08/addressing/soap/faults:Sendera:DestinationUnreachableThe message with To ‘’ cannot be processed at the receiver, due to an AddressFilter mismatch at the EndpointDispatcher. Check that the sender and receiver’s EndpointAddresses agree.”

<s:Envelope xmlns:s=“http://www.w3.org/2003/05/soap-envelope” xmlns:a=“WS-Addressing 1.0 Namespace”><s:Header><a:Action s:mustUnderstand=“1”>Web Services Addressing URI</a:Action></s:Header><s:Body><s:Fault><s:Code><s:Value>s:Sender</s:Value><s:Subcode><s:Value>a:DestinationUnreachable</s:Value></s:Subcode></s:Code><s:Reason><s:Text xml:lang=“en-US”>The message with To ‘’ cannot be processed at the receiver, due to an AddressFilter mismatch at the EndpointDispatcher. Check that the sender and receiver’s EndpointAddresses agree.</s:Text></s:Reason></s:Fault></s:Body></s:Envelope>

2

Hi @jeff.dawson,

Welcome to the community! :clap:

I will have to say doing SOAP and XML work in Postman is a bit more difficult that JSON, as there are many more things to SOAP that do not have handy helpers in Postman as they do in SOAPUI.

That said, because Postman is still basically sending of bare requests, you should be able to customize it the way you want to get the request to work. In particular, I was reviewing this article here from SOAPUI:

https://www.soapui.org/docs/soap-and-wsdl/supported-standards/using-ws-addressing/

What I would suggest doing is what they mention here. Review the request you made in SOAPUI by looking at the raw request, copy that into Postman, and then execute the script. It should ideally work. SOAPUI has handy helpers that help populate the requests with appropriate SOAP parameters to get the request to work, but at the end of the day, its still just any old request that any web clients can do, as its fundamental.

Hopefully this gets your request working in Postman!

Best,
Orest

3

Thank you Orest for all the info, really appreciate it! I’ll review and dig into this some more.

4

That did the trick and i was able to get a successful response back via Postman. I wanted to add one update incase anyone else comes across this. I noticed in SOAPUI when sending the SOAP xml request in the raw tab the actual SOAP body was not showing up. I had to open the preferences from File>Preferences or Ctrl+Alt+p > select UI Settings > check mark box “Wraps content in Raw Message Viewers”. After doing this I was able to pull the full soap message request and paste this into Postman with all the WSA headers required.

Thanks again!

2 Likes
5

Awesome! Glad you were able to figure it out, and thanks for leaving that additional information. Very helpful for future reference :slight_smile:

6

To clarify a bit (instead of using SoapUI to prepare a sample) this is minimum that you need to add in the raw XML request:

<soap12:Envelope xmlns:soap12="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
    <soap12:Header>
        <a:Action mustUnderstand="1">copy the action from WSDL's operation you are calling from WSDL file</a:Action>
        <a:To mustUnderstand="1">URL of a web service</a:To>
    </soap12:Header>
  <soap12:Body>
    your message body
  </soap12:Body>
</soap12:Envelope>
1 Like