Ryan Britton - 210 - Nov 4, 2014

Hi Demis,

I have a customer integrating into our SS services using SOAP, and they seem to be getting a set of illegal characters at the beginning of their SOAP Response Envelope?

see here :
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: application/soap+xml;charset=UTF-8;action="http://schemas.mosaic.co.za/types/SetParcelCommandResponse"
Server: Microsoft-IIS/8.5
X-AspNet-Version: 4.0.30319
Set-Cookie: ss-id=OrYbKT8vc0onW3jsDN2H; path=/; HttpOnly
Set-Cookie: ss-pid=LmI0wjpUmNSxx5ZtlPJY; expires=Sat, 04-Nov-2034 12:52:41 GMT; path=/; HttpOnly
X-Powered-By: ASP.NET
Date: Tue, 04 Nov 2014 12:52:41 GMT
Content-Length: 321

<?xml version=“1.0” encoding=“utf-8”?><s:Envelope xmlns:s=“http://www.w3.org/2003/05/soap-envelope”><s:Body><SetParcelCommandResult xmlns:i=“http://www.w3.org/2001/XMLSchema-instance” xmlns=“http://schemas.mosaic.co.za/types”><SetParcelReturn>Successful</SetParcelReturn></SetParcelCommandResult></s:Body></s:Envelope>

what could possibly be causing this?
The customer is using SOAPUI to test the SS services.

you can view the metadata for the request in question over here :


It’s most likely the UTF-8 BOM character, is this causing an issue with the SOAPUI?

Ryan Britton:

Yes…what do you recommend as a fix?

It’s something that’s automatically emitted by the Xml Serializer, I’ll have to investigate to see what can be done to prevent it.

Hi Ryan, the UTF8 BOM character should no longer be emitted in SOAP responses in this commit:

This change is now on MyGet:

Ryan Britton:

you never disappoint, Demis.

It is really a pleasure dealing with you on an ongoing basis and sharing in the ServiceStack Journey. License fees are very often a grudge payment in this day and age - but my contribution to SS is worth every penny and more.

Thank you :slight_smile: