WebService, as everyone must be familiar with, is a way for a "service provider" to provide services to a "service caller". There are several key technologies in it:
XML: A standard method for describing data
SOAP: Simple Object Access Protocol, used for information exchange
WSDL: Web Service Description Language
UDDI: Universal Description, discovery and integration, it is a platform-independent, XML-based protocol for describing commerce on the Internet.
SOAP transmits UTF-8 encoding by default, which also determines that WebService also uses UTF-8 encoding by default.
The project I am maintaining now is a PHP project, and all coding uses GBK. When calling the WebService method provided by itself, you will encounter coding problems. The PHP page calls WebService, and this WebService calls another PHP class that calls COM components. This is probably the scene.
Copy code The code is as follows:
PHP page (GBK) -> WebService (UTF-8) -> PHP Class (GBK)
Before I encountered any problems, everything was calm, and it was like this for many years. One day, the company acquired other companies. In order to integrate services, user information was also integrated. The accounts of all users of the original company were composed of English characters and numbers. However, the acquired company did not make such restrictions. The accounts had The case of Chinese characters. After integration, the problem occurred, "error in msg parsing: XML error parsing SOAP payload on line 1: Invalid character [detail]"!
I have just come into contact with PHP, so I am not very familiar with it, and the debugging of NetBeans is very difficult. So open VS, reference WebService, and start testing. The returned result cannot find the user, and it is garbled. OK, after looking at it, it is caused by inconsistent encoding when the UTF-8 encoding of WebService is passed to the PHP class! Convert it to GBK and then transmit it. After receiving the data, the user is found, but it is still garbled. After converting the returned data to UTF-8 again, everything is OK! Tested under VS everything is normal! Get on the test machine! Start testing! After opening it, garbled characters! Still "error in msg parsing: XML error parsing SOAP payload on line 1: Invalid character [detail]" Sorry!
Calm down and continue the analysis! It should be caused by the PHP page calling WebService! The test page under VS is UTF-8, and there is no problem between them, but the page in PHP is GBK. After revising again, everything returned to calm.
Copy code The code is as follows:
Call: PHP page, parameters are converted to UTF-8 -> WebService, converted to After GBK -> PHP class
returns: PHP class -> WebService, converted to UTF-8 after received -> PHP page, converted to GBK
http://www.bkjia.com/PHPjc/321952.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/321952.htmlTechArticleWebService, everyone must be familiar with it, is a service provided by the "service provider" to the "service caller" One way. There are several key technologies in it: XML: a standard for describing data...