[2010-04-18 15:44 UTC] reigo at reinmets dot ee

I've  been looking everywhere to find a fix for this.. Thank you very much. 

My problem being, that i have a b2b application where the other end is saying:
HTTP: Cannot process the message because the content type 'text/xml; charset=utf-
8' was not the expected type 'application/soap+xml; charset=utf-8'.

And ofcourse the ability to change it in PHP side.. of right, no ability :(

 [2010-05-28 14:18 UTC] dmitry@php.net

 [2010-05-28 14:18 UTC] dmitry@php.net

This bug has been fixed in SVN.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
 
Thank you for the report, and for helping us make PHP better.

 [2010-07-09 16:17 UTC] henri at asseily dot com

It's good that the authorization header is not silently discarded any more, but 
that solution in the snapshot is suboptimal at best.
It requires the auth header to be set in the context, when instead a simple 
'authorization' parameter in the constructor could allow the user to pass in 
anything, including custom-built or cached auth headers such as the OAuth header.