title: Problems with MSXML2.SERVERXMLHTTP in Classic ASP
body: <p>Right now I'm trying to connect from a Classic ASP VBScript page to an ASP.NET page via HTTPS using this pattern:</p>
  
  <pre><code>Dim url
  Set url = "https://domain/dir/dir/dir/Page.aspx?foo=1&amp;bar=2"
  Set objxmlhttp = server.CreateObject("MSXML2.SERVERXMLHTTP")
  
  objxmlhttp.Open "POST", url, False 
  
  If Err.Number &lt;&gt; 0 Then
      Response.Write "Ready state is: " &amp; objxmlhttp.readystate &amp; "&lt;br&gt;"
      Call UnAuthorizedUsage("HTTP_VALIDATE_OPEN")
  End If
  
  objxmlhttp.Send
  If Err.Number &lt;&gt; 0 Then
      Response.Write "Ready state is: " &amp; objxmlhttp.readystate &amp; "&lt;br&gt;"
      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
  </code></pre>
  
  <p>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.</p>
  
  <p>However, the strange thing is, when I put in a bogus URL, the error message's ready state is still 1 (<a href="http://www.w3schools.com/dom/dom_http.asp" rel="nofollow">as per the documentation, 1 is "<strong>server connection established</strong>"</a>). This leads me to believe that this script isn't able to connect to anything at all.</p>
  
  <p>Is there something I'm missing? What network settings could there be that can be blocking this from happening?</p>
  
  <p>Thank you</p>