intermittant problems

Here's a weird one, One of our client sites works fine on every computer in our office (and no these arent terribly fast machines), and for most of the users that access it. However, certain users (we havent been able to establish a pattern yet) are having issues trying to save data. We've made no changes to the code, but we have done a couple of database restores in the past few days. We've managed to reproduce the problem by remoting into one of our webservers (we have multiple providers) and running the process. The only failure I can find is a javascript failure, there's a crapload of bulky YUI code in here. Any thoughts?

Have you tried firebug to see what is failing in the JS? I'm presuming an ajax call. And have you tried doing a traceroute from that machine to see if there is a problem upstream from your server? Cheers, Judah On Thu, Jun 7, 2012 at 10:42 AM, Scott Stewart <webmaster@sstwebworks.com> wrote: ----- Excess quoted text cut - see Original Post for more -----

Yeah, we've looked through firebug and it says O is not defined (I didn't write this). I can only assume that O contains a recordset... The traceroute times look pretty slow once it gets into the provider's network (84 - 100ms vs. 6 - 10ms) We've got a call into our provider to see if there's anything that they're willing to tell us. On 6/7/2012 2:07 PM, Judah McAuley wrote: ----- Excess quoted text cut - see Original Post for more -----

You should be able to see what O is by running Firebug in a spot where the request is successful. 100ms isn't really that slow. Is it dropping packets at all? And what is the HTTP Response code of the ajax call? A 504 timeout? 503 Not Available? If you can correlate the connection response in Firebug with the the connection in the web server logs, you might be able to come up with a reason why. Judah On Thu, Jun 7, 2012 at 11:40 AM, Scott Stewart <webmaster@sstwebworks.com> wrote: ----- Excess quoted text cut - see Original Post for more -----

We fixed it, there was a point in one of the YUI calls where it was calling a fully qualified URL that was an "http" instead of an "https". On 6/7/2012 2:07 PM, Judah McAuley wrote: ----- Excess quoted text cut - see Original Post for more -----

That can be a tricky one. We had a problem with that recently where some customers were complaining that they would take an action on the site and then get "logged out". Turns out that there were some http calls to cdns for jquery on an otherwise https site. On certain configurations of IE it would trigger mixed content warnings that would show a little button down at the bottom of the page that they didn't notice while the main page would be showing our non-logged in content because it was stopped by the browser mid-redirect. D'oh. Judah ----- Excess quoted text cut - see Original Post for more -----

what do you mean by save data ? that is very ambiguous as there are many ways to save data, via a form, via FTP, via RDP, via unc path, etc On Thu, Jun 7, 2012 at 6:42 PM, Scott Stewart <webmaster@sstwebworks.com>wrote: ----- Excess quoted text cut - see Original Post for more -----