How to test an AJAX installation

Is there a simple and reliable way to check the AJAX installation? We have a problem when we call a web page using an AJAX form JS file. The error "ServiceLib" is undefined. The error causes multiple hits on Google.

We have added some AJAX functionality to the client application. This works great here in the office on dev machines and on our IIS server, it works great on the client's website, but when we put the application on the site in real time, the web page calls fail.

The client installed AJAX on their backend server a few days ago. We have verified that the service lib files are there and in the right places.

We've already spent hours on this without a solution and still don't know for sure if there is something wrong with our code, or something wrong on their server, or, for that matter, whether AJAX is installed correctly. Part of our problem is that we don't have access to their live server, so we can't do anything other than change our own code, give the app files to our contacts, and see what happens. Contact knows less than we do, which is why we work blind. Strange situation, I know, but there is a system involved.

Thanks a lot Mike Thomas

+1


source to share


2 answers


Firebug can help - if you can get someone at the far end to install it, it can give you an idea of ​​what's going on with ajax requests through a console that logs and gives you the ability to view the return data of all ajax requests.



+1


source


I think...

There are three parts to the process:
1) The client-side javascript logic in the browser sends an HTTP request to the server.
2) The ASP.NET server page processes it and responds.
3) The client logic gets the response and refreshes the web page or whatever.

Swap each part with something simpler and more diagnostic to see where the pipeline is.



For example, create a diagnostic web page that replaces # 1, which calls the server page directly.

If that works, create another ASP.NET server side page that is very simple, just register something to prove the real # 1 does what your # 1 diagnostic did.

I know your standard debug binary search ...

0


source







All Articles