When the customer calls a WebService written by me using SOAP (this wes was created by using heavy loads, several different messagename were set, and Chinese characters were used for convenience :(), the result is always prompted"
The server fails to recognize the value of the HTTP header soapaction.".
I searched for it and thought it was a WebService namespace problem. I tested it.
Enable httppost and httpget to call WebServices and use XMLHTTP. Normal.
Because the customer does not use the proxy class or XMLHTTP method but uses soap to call WSE, he writes a leaf for PHP to call WSE (nusoap call, this is soap anyway ), then we can see"System. Web. Services. Protocols. soapexception: server did not recognize the value of HTTP header soapaction ".
No suitable materials were found (because no one named the messagename Attribute-_-! in Chinese -_-!), Later I felt the error prompt is a bunch of garbled characters behind, I guess it is not a Chinese problem, even though the soap and WSE are set UTF-8. Try to modify messagename to English, finally normal.
We haven't tested the use of DOTNET or ASP to call with soap, but it should be no different from PhP...
PS: Which Big Guy can find a way to support Chinese?
Reminder: Do not use spaces in messagename ..