Question

Right now I’m trying to connect from a Classic ASP VBScript page to an ASP.NET page via HTTPS using this pattern:

Dim url
Set url = "https://domain/dir/dir/dir/Page.aspx?foo=1&bar=2"
Set objxmlhttp = server.CreateObject("MSXML2.SERVERXMLHTTP")

objxmlhttp.Open "POST", url, False 

If Err.Number <> 0 Then
    Response.Write "Ready state is: " & objxmlhttp.readystate & "<br>"
    Call UnAuthorizedUsage("HTTP_VALIDATE_OPEN")
End If

objxmlhttp.Send
If Err.Number <> 0 Then
    Response.Write "Ready state is: " & objxmlhttp.readystate & "<br>"
    Call UnAuthorizedUsage("HTTP_VALIDATE_SEND")
End If
On Error GoTo 0:

If objxmlhttp.Status = 200  then
    If objxmlhttp.responsetext = "Blah blah blah" Then
        Response.Write "Everything works!"
End if
Set objxmlhttp = Nothing

Everything is communicating properly when I’m run this on my local machine, but when I move it to the production server, it just breaks. I get stuck on readystate 1, and there is no communication whatsoever.

However, the strange thing is, when I put in a bogus URL, the error message’s ready state is still 1 (as per the documentation, 1 is “server connection established“). This leads me to believe that this script isn’t able to connect to anything at all.

Is there something I’m missing? What network settings could there be that can be blocking this from happening?

Thank you

Answer 1

Have you run the ProxyCFG tool on the server?