in

ASP.NET Weblogs

uber1024's WebLog

It's not hot wings and beer, but it's still okay

Problems with AJAX on secure servers

At my company, we use a hand-rolled AJAX solution (it's about 2-3 years old, otherwise we probably would have used someone else's solution).  Recently, we've applied it to one of our secure (HTTPS) websites and we've been having intermittant problems with the XMLHTTP object on the browser (always IE 5.5+) sending requests to the server (always Win2k3).  It happens about once every 20-25 requests and just returns an error message that says "The download of the specified resource has failed."  We tried moving our web service to an HTTP server rather than an HTTPS server and the problem went away, so we're fairly certain that it's a problem with the XMLHTTP object communicating with the secure server, and we've tried stripping out all irrelevant code, so we're also fairly certain that it's not something unrelated. 

We've contact Microsoft support about this and they've confirmed that we're not the first people to encounter this problem but haven't gotten any more info from them yet (although we should hear back soon).

This is just an FYI for those of you jumping on the AJAX bandwagon from someone who's been doing this sort of thing for a while now.

Comments

 

Gabriel Halsmer said:

I'm interested in what you find out from MS. From my experience, we've been running an HTTPS site using XmlHttp since Jan. 1st, 2002. And we've never encountered intermittent problems with XmlHttp.

BTW, which version of XmlHttp do you use. I believe there are 3 that a client's PC could have (version 2.0, 3.0 and 4.0). Most Ajax solutions I've seen try to use the most recent one and revert back to older versions if need be. We actually just stuck with version 2.0 since that had the widest market penetration and using a single version made testing easier.
January 3, 2006 1:34 PM
 

Dave said:

I would suggest eliminating your reliance on the xmlhttp object. Its always been flakey. We've used an Iframe as the communication transport for "AJAX" for years now with no issues.

Back on xmlhttp it also became a client per client issue. Worked fine on some not on others. Not an issue you want to deal with when you have thousands of users.
January 3, 2006 1:57 PM

Leave a Comment

(required)  
(optional)
(required)  
Add