Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.13.0

Bug #10023 unquoted type parameter text/xml when using HTTP transport and mime attachments
Submitted: 2007-02-04 13:21 UTC Modified: 2007-06-29 09:59 UTC
From: damjan dot glad at zejn dot si Assigned: yunosh
Status: Closed Package: SOAP (version 0.10.1)
PHP Version: 5.1.4 OS: Windows XP
Roadmaps: (Not assigned)    
Subscription  


 [2007-02-04 13:21 UTC] damjan dot glad at zejn dot si (Damjan Glad)
Description: ------------ When using mime attachments and HTTP transport the resulting HTTP request is invalid. Problem is that "type" parameter in Content-Type header is not quoted. This is not HTTP compliant, e.g. Axis will reject such requests. This is how the HTTP header type parameter is currently generated: Content-Type: multipart/related; type=text/xml; This is the correct HTTP header type parameter (it is quoted): Content-Type: multipart/related; type="text/xml"; Test script: --------------- function SOAP_Base::_makeMimeMessage defines the content type in the following line: $params = array('content_type' => 'multipart/related; type=text/xml'); Changing this line to: $params = array('content_type' => 'multipart/related; type="text/xml"'); solves the bug. But the same function is also reused in other contexts: - SOAP_Server_Email::service - SOAP_Server_Email_Gateway::service - SOAP_Server::service I did not check if the above mentioned "fix" is the right thing to do when called from other three locations. This should be verified and corrected if needed.

Comments

 [2007-02-05 04:16 UTC] yunosh (Jan Schneider)
If fixed this locally. But since I have other changes in the file that have not been tested yet, I'm gonna commit your fix later.
 [2007-06-29 09:59 UTC] yunosh (Jan Schneider)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.