Re: [SOAP] bug in _decodeDIMEMessage

Not as far as I can see. The changes either fix obvious bugs (DIME.diff) or fix problems without changing existing behaviour for other clients. Brodie. LIMBOURG Arnaud wrote:

Hi, Can those diff induce compatibility problems with earlier versions ? Arnaud.

Hi, I had problems with the decoding of a DIME response sent by a gSoap server. It seems that gSoap uses the 'cid:' prefix in both the SOAP message body, and in the header of the DIME attachment. PEAR::SOAP expects that only the body will have the prefix and not the attachment header. It therefore plugs another prefix onto it ending up with an attachment table with id's like 'cid:cid:id1'. I have fixed the _decodeDIMEMessage() function to handle having the 'cid:' prefix in both locations, plus fixed a couple of other bugs: * return after raising a fault * checking for an error in the decode * remove the duplicate call to strcasecmp() I've attached the diff -u8 to fix this problem. I've also fixed a spelling error in the DIME.php file, the diff -u8 for that is also attached. Another problem that I'm having at the moment which I can't track down though is a PHP error: [16-Jul-2003 12:19:01] PHP Fatal error: Call to undefined function: _decodedimemessage() in c:\php\pear\SOAP\Transport\HTTP.php on line 353 For some reason it isn't finding the _decodeDIMEMessage() function in the base class SOAP_Base_Object. I have to move the function into the SOAP_Transport_HTTP class for it to be seen. Any ideas? Brodie.