Yes, it's not a SOAP problem but an interoperability known problem.
When you send an HTTP request avoid all blank in content-type
header variable.
Notice that if you send "content-type:text/xml; charset=utf-8"
in an HTTP request, the common servlet method getEncoding() return
null. If you remove the blank between "text/xml;" and "charset=utf-8"
the getEncoding method return utf-8 !!!
Hope that help
Jean-Louis
> -----Message d'origine-----
> De : Colin Saxton [mailto:[EMAIL PROTECTED]]
> Envoy� : mercredi 6 juin 2001 10:26
> � : '[EMAIL PROTECTED]'
> Cc : Thomas Greenwood
> Objet : IIS and Apache SOAP Client
>
>
> Apache SOAP client does not work on IIS. IIS sends:
> ...
> Content-Type:text/xml; charset=utf-8
> ...
>
> Where as Apache sends
>
> ...
> Content-Type: text/xml; charset=utf-8
> ...
>
> Notice the extra space after "Content-Type:".
>
> An Exception is thrown in the SOAP client (GetAddress example) that states
> the content type should be text/xml but it is read as ext/xml?? I
> think this
> is because of the extra space...has anyone had this problem?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
