You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 14, 2023. It is now read-only.
For the most part this issue doesn't affect that many SOAP clients, but I have observed that some .NET SOAP clients attempting to consume a web service from Silverstripe will fail with the following error:
Client found response content type of 'text/html; charset="utf-8"', but expected 'text/xml'.
The request failed with an empty response.
The solution is simply to explicitly set the content type in the index() action with a line of code like this:
Note that a similar explicit setting of the header already occurs in the wsdl() action, I believe it is an oversight that it isn't also in the index() action.
Thanks & regards,
Adrian Logue
The text was updated successfully, but these errors were encountered:
For the most part this issue doesn't affect that many SOAP clients, but I have observed that some .NET SOAP clients attempting to consume a web service from Silverstripe will fail with the following error:
The solution is simply to explicitly set the content type in the index() action with a line of code like this:
Note that a similar explicit setting of the header already occurs in the wsdl() action, I believe it is an oversight that it isn't also in the index() action.
Thanks & regards,
Adrian Logue
The text was updated successfully, but these errors were encountered: