go to bug id or search bugs for
This patch adds support to add headers into the http context, but doesn't allow the Authorization header for some reason.
I added a patch to our 5.2 build that would add all headers in the http context and remove that patch in 5.3 because I noticed the above patch. Somebody at work is needing to add Authorization header to get OAuth stuff working, but for some reason it is not allowed.
Here is a patch that will allow the Authorization header:
Here is an example script that requires the Authorization when used for the OAuth stuff.
Add a Patch
Add a Pull Request
I am removing oauthsoapsample.php.txt as there was bad code in that and mail asked me to remove it.
I have added:
which has multiple scripts that show the problem.
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 :(
Automatic comment from SVN on behalf of dmitry
Log: Fixed bug #50976 (Soap headers Authorization not allowed)
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
Thank you for the report, and for helping us make PHP better.
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.