var xmlRequest = new ActiveXObject("Microsoft.XMLHTTP") //kickoff the queue processing asynchronously
xmlRequest.open("GET", "ProcessQ.asp?OrderID=123", true)
xmlRequest = null
As you can see it's making an asynchronous call, due to the fact that the page being hit does heavy processing and I don't want the browser page to have to wait for completion. The page that contains this function runs under SSL. The asp page that the function is calling redirects itself to http once it is hit. I would think the js function has no knowledge of this because (1) the context switch happens on the server and (2) the call is asynchronous.
This web app has been deployed to several different servers. On some servers it seems to run fine. On other servers, the client browser displays a security warning when the processQ function runs: "This page is accessing information that is not under its control. This poses a security risk. Do you want to continue? (Y/N)"
When SSL is turned off, this security warning is not thrown. So it seems to relate to SSL.
So I'm trying to understand why this security warning is thrown given that (1) the ProcessQ.asp page is in the same folder as the page containing the processQ function and (2) the call to ProcessQ.asp is a relative url path -- it's not like it's trying to hit some page on another server or a different virtual directory.
Also, on some xp sp2 IE6 browsers, the processQ function appears to fail silently and sporadically. Is there a particular browser security setting that would cause either or both of these problems? What is the best solution here?