|
Hai
>>>>>>>>>>
If the Content-Type header says the charset is
UTF-8 and the XML declaration specifies ISO-8859-1 encoding, the implementation
is faulty and the SOAP message should be rejected.
<<<<<<<<<<
When there is a Content type header then you can
check for both XML declaration and Content Type to check the encoding is same or
diffrent.
But in my case there was no content type at
all.Thats why i said so.I do accept that its always best that make
encoding depending upon the Content Type and not on XML
decleration.
>>>>>>>>
The fault in your case is NuSOAP, which incorrectly
assumes a charset of UTF-8 if the HTTP Content-Type header does not specify a
charset.
The HTTP 1.1 spec says that NuSOAP should assume
ISO-8859-1 in this case.
<<<<<<<
This is correct.But before it was set to UTF8.So
that was creating the total problem.
Bcas the encoding was in UTF8 and the soap
defencoding variable was set to ISO.
>>>>>>>>>>
NuSOAP has been fixed (although the fix is not yet
in CVS), and it now also has code to detect erroneous SOAP messages in which the
HTTP
Content-Type and XML declaration specify different
encodings.
<<<<<<<<<
That is one more good thing which has been
done.
Regards
Sathish
Sathish Chandrasekar
eMacmillan, eBusiness-
Division
Macmillan India Ltd.
Floor 8th, Brigade Towers
135 Brigade
Road
Bangalore- 560 025, India
| 
