Re: Antwort: Re: HTTPAPI - Problem consuming WCF webservice - HTTP/1.1 400 Bad Request

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

Aha!  I missed that he specified the charset in the content-type!  That 
certainly explains the problem...   if you tell it that the 
charset=utf-8 in the content-type, and specify <?xml 
encoding="iso-8859-1" ?> in the processing declarations, you are clearly 
giving the web service conflicting information.

So it's rejecting the iso-8859-1 (even though that _is_ what is being 
sent) because Kevin already told the web service that it's utf-8.


On 9/14/2010 2:06 PM, Thomas Raddatz wrote:
>
>     New iconv() objects set, PostRem=819. PostLoc=0. ProtRem=819. ProtLoc=0
>
> But the content type is set to "utf-8":
>
>     Content-Type: text/xml; charset=utf-8
>
> I wonder what encoding actually is expected by the web service.
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------