In these two days, CRM, one of the key development branches of the Department, went online. JQuery is used to call WebService through Ajax. An inexplicable 404 error was reported during the test. After analysis, 404 it is because the error page error.aspx configured by web.config itself does not exist, so this error makes it confusing to find the real reason. In the final analysis, it is lack of experience.
after this error is eliminated, the real cause of the error is that 500 errors are reported, which is correct locally; It is also correct to directly enter the server for testing; Open the browser remote call, and an error will be reported. It’s obvious that Google keyword: jQuery reports errors when calling WebService remotely. There are a lot of solutions, which are simple and effective. Here’s a record:
It turns out that the default post setting in web.config does not allow remote calling of WebService. Just change the configuration.
if you want to call it normally remotely, you need to modify web.config and add the following paragraph under the system.web section
<webServices > <protocols > <add name="HttpSoap"/> <add name="HttpPost"/> <add name="HttpGet"/> <add name="Documentation"/> </protocols> </webServices>
- SoapUI Call Error: error reading xmlstreamreader [How to Solve]
- JQuery Error: TypeError: jQuery.curCSS is not a function [How to Solve]
- [jQuery version] cannot read property ‘MSIE’ of undefined solution
- [Solved] item2 Error: a session ended very soon after starting. check that the command in profile default
- [Solved] jQuery Error: Uncaught ReferenceError: $ is not defined
- Git Error: fatal: remote origin already exists.
- [Solved] Jquery ajax “Uncaught TypeError: Illegal invocation”
- [Solved] npm install Error: github requires permissions, Permission denied (publickey)
- Unknownhostexception: XXX, an error is reported when using the Nacos remote call service (load balancing)
- [Solved] Javax.naming.NameNotFoundException: Name jdbc is not bound in this Context