Login Register
Home » Support » Forums » Dojo Core (dojo.*, 0.9+) » Dojo Core Support » XHR, SSL, and (12152 errors OR Timeouts)

XHR, SSL, and (12152 errors OR Timeouts)

Submitted by gid on Thu, 02/28/2008 - 22:28.

I'm working on a web app using dojo 0.9 (work is underway to upgrade to 1.0.2) that is accessed exclusively over SSL with both IE6 and IE7.

When issuing a dojo.xhrPost() seemingly at random it will error out with a 12152 error and other times, it will error it will eventually timeout. IE7 seems to only timeout, but IE6 gives the 12152 error as well as timeouts. The situation seems to be worse at peak times of the day, and using a wireless connection seems to make matters worse. Just using my cable modem at home I'm unable to reproduce the problem, but was able to reproduce it at two different locations the other day, both on a wired and wireless connection. (but again wireless seems worse)

I came across this forum post http://www.perkiset.org/forum/ajax/xmlhttprequest_ie6_ssl_and_12030_erro... which for the most part explains our problem, the suggested solution at the very end of the post seems to possibly fix the 12152 error with IE6 (I added bindArgs['headers'] = {"Connection": "close"}; to xhrPost()), but the timeouts are still happening.

Currently the application doesn't work well with firefox, but we eventually plan to test with that as well which should hopefully work better.

Does dojo attempt to work around these errors and timeouts or is it possible to reliably work around these errors?
If not, what can be done to reduce these errors, short of ditching XHR?
Does 1.0.2 fix anything related to the above problems?

Any suggestions would be greatly appreciated.

‹ DND not working Incorrect values of checkboxes when dnd-ing rows with IE ›

I should add we occasionally

Submitted by gid on Mon, 03/03/2008 - 16:04.

I should add we occasionally get 12030 error status codes and possibly others as well.

I do not have any specific

Submitted by jburke on Mon, 03/03/2008 - 17:13.

I do not have any specific advice for this area, but just noting that dojo does not do anything specific for SSL or for 12152/12030 errors. It just wraps the normal XMLHttpRequest functionality in the browser. No changes in 1.0.2 either.

It seems like at least one other person has used dojo successfully in an SSL environment, so my first inclination is to assume that dojo is not introducing a problem for that environment.

Thanks for the reply. I

Submitted by gid on Tue, 03/04/2008 - 20:04.

Thanks for the reply. I don't specifically blame dojo, I tend to blame Microsoft's implementation of XHR while over ssl.

I just need a reliable way to work around/avoid/eliminate the errors XHR is throwing back at us.

Did you find a solution?

Submitted by gloewy on Tue, 04/29/2008 - 09:46.

I see the same behaviour with IE7 and non secure transport.

Unfortunately no solution

Submitted by gid on Tue, 04/29/2008 - 18:12.

Unfortunately no solution has been found as of yet. We've experimented with a number of different approaches, but nothing seems to work 100% of the time yet.

We did a number of things to

Submitted by gid on Mon, 05/19/2008 - 14:01.

We did a number of things to hopefully work around these errors. It's hard to say what actually fixed it since we could never reliably reproduce the issue. But we tried changing the gzip library we're using to compress the code, upgrading the j2ee java server itself, in our case Oracle IAS, and also upped the keepalive timeout to 60 seconds (the max limit that IE uses).

We have had any complaints in awhile, so it would seem one of the above changes worked.