Description:
------------
When making a SOAP call in non-WSDL mode toward a .NET service, SoapClient adds 
a pound sign (#) instead of a 
slash (/) between URI and action, which makes the .NET service return: "Server 
did not recognize the value of HTTP 
Header SOAPAction: <uri>#<action>".

According to previous bug-report #30370 (which is similar), this is not a bug: 
"If you don't use WSDL then you 
should specify "soapaction" by your self". 

However, adding a soapaction definition is only possible with __call / 
__soapCall and not when calling a WSDL 
function directly. I think this is not an issue when calling a PHP SOAP server 
since it probably interprets the 
pound sign correctly. A .NET SOAP service will not, however.

To make it easier, it would be desirable to be able to define SOAPAction, or be 
able to define a .NET compability 
mode even when calling a WSDL function, since being limited to using the low-
level __soapCall requires structuring 
the call by yourself.

Test script:
---------------
$client = new SoapClient(NULL,array(
  "host"=>"http://host/action.asmx",
  "uri"=>"http://host/webservices/soaprequest"
);
$info = $client->Action($options,$ctx,$wfl);


Expected result:
----------------
Fatal error: Uncaught SoapFault exception: [soap:Client] Server did not recognize 
the value of HTTP Header SOAPAction: http://host/webservices/soaprequest#Action