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

Bug #6213 Wrong Content-Type on HTTPS requests
Submitted: 2005-12-09 17:41 UTC
From: rbro at hotmail dot com Assigned: cweiske
Status: Closed Package: SOAP
PHP Version: 5.0.5 OS: Linux
Roadmaps: (Not assigned)    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 49 + 30 = ?

 
 [2005-12-09 17:41 UTC] rbro at hotmail dot com
Description: ------------ When sending a multipart/related SOAP message (a message with a SOAP attachment) to a HTTPS URL, the Content-Type is not preserved. Instead of "multipart/related", a Content-Type of "text/xml" is sent. Line 572 of Transport/HTTP.php has: curl_setopt($ch, CURLOPT_HTTPHEADER , array('Content-Type: text/xml;charset=' . $this->encoding, 'SOAPA ction: "'.$options['soapaction'].'"')); I believe it instead should be something like: if (!isset($options['headers']['Content-Type'])) { $options['headers']['Content-Type'] = 'text/xml'; } curl_setopt($ch, CURLOPT_HTTPHEADER , array('Content-Type: '. $options['headers']['Content-Type'].';charset=' . $this->encoding, 'SOAPAction: "'.$o ptions['soapaction'].'"'));

Comments

 [2006-01-08 01:25 UTC] yunosh
This code will go away soon anyway.
 [2006-03-09 14:13 UTC] rbro at hotmail dot com
Do you know when this code will be rewritten? In the meantime, I am running a modified version of PEAR SOAP to resolve this problem. Thanks.
 [2007-02-23 20:58 UTC] danielc (Daniel Convissor)
This code is still in there. Perhaps you want to reconsider the decision to mark this "won't fix"?
 [2007-06-27 15:18 UTC] cweiske (Christian Weiske)
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. I comitted the fix; it can always be removed as long as it will take :)