views:

18

answers:

1

I know this sounds odd. The JS on my project functions perfectly, except when the web site is accessed using computers at one specific company. To make things even more difficult, the JS fails only about 50% of the time when run from that company. The JS failure occurs with FireFox, Chrome, and IE.

I have tested this myself using FF and Chrome on a thumb drive. The browsers on my thumb always display my project site perfectly, except when run from a computer on said company's network where they fail at the same rate as the installed browsers.

My JS is using jQuery and making some Ajax calls. The Ajax calls are where the failure is occurring. To diagnose the problem I created a logging function for my Ajax calls and recorded success and failure. Over a one month period, there were only a handful of failures (about 1%) from all access points other than this company. Oddly enough, the Ajax calls in the logging function are not failing.

There is nothing exotic there - Just Win XP SP3. I have never noticed any other unusual behavior from their network. The company is a division of a mega ISP and is on their corporate network.

Any other suggestions for troubleshooting would be welcome.

A: 

Maybe they have some data protection software installed (against data theft) they are not telling their employees about? It might account for the arbitrary (but notable) fail rate, rather than a firewall that would presumably block all traffic.

I would look in the company PC's task manager / process list and compare the list of running programs to a "normal" XP3 SP3 installation. Also, I would talk to the admins whether any protective measures are in place - with a big ISP, I imagine there might well be.

Just shooting in the dark, of course.

Pekka
I don't think so. I know the calls are going out because I am receiving JSON from the remote.
@uku What do the calls return when they fail? Are you catching failing calls with an error handler that can give you status code and error message?
Pekka
@Pekka, The response just contains a generic error message - No detail about whether the request was malformed.
@uku can't you extend that? Shouldn't the error handler return `statusText`/`responseText`/`statusCode` or similar fields to work with? Or does it not populate any of these fields?
Pekka