NHSDigital/integration-adaptor-mhs

Synchronous message response returned in unexpected SOAP envelope

Closed this issue · 2 comments

davesmith9088 commented

When using synchronous messaging (example request file attached to this issue) the response is returned
as a SOAP response, which seems incorrect as the API does not take a SOAP request.

If we use an async message (request attached) with the wait-for-response header set to true,
then we just get the response XML without the SOAP envelope (as expected)

Looks like a bug as types of payload we are getting back are inconsistent and seem to depend on the interaction type.

The issue can be recreated by sending the message payload in the example "MHS sync request.txt" file via CURL or postman.
This is for OpenTest, the ASID will need to be changed according to your Open Test connection details.

MHS async request.txt
MHS async response.txt
MHS sync request.txt
MHS sync response.txt

petervdm commented

Thanks for reporting this @davesmith9088, we'll add a ticket for it and get it looked at