When IIS accesses the webservice written in PHP, the error 404 is reported. However, my machine can respond and log on to the server.

When IIS accesses the webservice written in PHP, the error 404 is reported. However, when my machine accesses the webservice, I can respond and log on to the Server for Windows 7 and the same machine for two websites,
Website 1 is written in ASP. NET and published on port 8080 of IIS
Website 2 is written in PHP and published on APACH of the same machine, port 80

Both sites can be accessed and can be logged on. there is no problem with data interaction. However, an HTTP 404 error is reported when. net calls PHP's WEBSERVICE.
But we can do it locally. Is there a problem with the configuration,

Urgent, online, etc.

Reply to discussion (solution)

404 indicates that the page does not exist. check whether the address you called is wrong.

404 indicates that the page does not exist. check whether the address you called is wrong.

No error is Reported. the. NET and PHP code are correct. on The Local. NET call server, PHP and PHP call Server. NET, data can interact normally.

Is the wsdl correct?

Is the wsdl correct?

Correct. I will directly refer to

This is now the case. the two sets of code are deployed on the same machine, and data is directly written to each other on the website. The WEBSERVICE cannot be accessed. in front of this, I put the PHP code in it, change the WSDL address to localhost, and then the PHP Data can be transferred to each other. net. However, the two sets of code should be separately deployed on the two machines. Is there a routing problem on the server.

Another phenomenon is that before I change the code (not changed to localhost), we can access the site to create data on both sides, however, it is easy for the Japanese to build data in Japan, and it is also through the site.

Isn't your client wrong?

Isn't your client wrong?

However, my local PHP client code calls the server IP address, and the data can be synchronized. The original code on the server is the same as my local code, but the site cannot be synchronized. Later, I tried to change the server code to LOCALHOST so that the site can be synchronized, because the. NET code is also local. Then, I opened the IE access site on the server, but the site could not be accessed. So is it a problem with the routing settings? No problem with the code

Isn't your client wrong?

Now. NET can do data. Or is it a problem with APACH or IIS configuration?

The question is about route settings over there... Paste