WCF-BasicHttp : Response binding ISO8859-1 instead of utf-8 by BizTalk - Paris

I forgot one important step in my workaround:

Step 4:
Modify your CustomTextMessageEncoder class to add the following override:

        public override bool IsContentTypeSupported(string contentType)
        {
            return true;
        }

This will allow you to receive ISO-8859-1 encoded XML data from a non-Microsoft web server.

I have successfully created a work around for this problem, although it currently only works if you know in advance that the service you are about to contact returns ISO-8859-1 encoded data.

Step 1:
Follow the instructions described by this Custom Text Encoder example: http://msdn.microsoft.com/en-us/library/ms751486.aspx

Step 2:
Modify your CustomTextMessageBindingElement class by adding the following overrides:

        public override IChannelFactory<TChannel> BuildChannelFactory<TChannel>(BindingContext context)
        {
            context.BindingParameters.Add(this);

            return base.BuildChannelFactory<TChannel>(context);
        }

        public override IChannelListener<TChannel> BuildChannelListener<TChannel>(BindingContext context)
        {
            context.BindingParameters.Add(this);

            return base.BuildChannelListener<TChannel>(context);
        }

        public override bool CanBuildChannelFactory<TChannel>(BindingContext context)
        {
            context.BindingParameters.Add(this);

            return base.CanBuildChannelFactory<TChannel>(context);
        }

        public override bool CanBuildChannelListener<TChannel>(BindingContext context)
        {
            context.BindingParameters.Add(this);

            return base.CanBuildChannelListener<TChannel>(context);
        }


Step 3:
Modify your code (or web.config) to use an instance of the CustomTextMessageBindingElement class above.

This worked for me, but only if configured properly before the ISO-8859-1 service is contacted. I will continue to research if the custom message encoder can be further modified to handle SOAP messages using any encoding value, and will add more information as it becomes available.