All Things WinBatch > WebBatch

HTTPS via MSXML2.XMLHTTP

(1/2) > >>

JTaylor:
The following code works as a WinBatch Script with HTTP and HTTPS and it works with WebBatch if I use HTTP but not HTTPS.   Is this expected behavior?

I get a response of:

1261:  COM/CLR: Exception

MSXMLHTTP.Send

Jim


--- Code: Winbatch ---    MSXMLHTTP = CreateObject("MSXML2.XMLHTTP.6.0")
    MSXMLHTTP.Open("GET", XMLURL, @FALSE)
    MSXMLHTTP.Send
    xtxt = MSXMLHTTP.ResponseText
    ObjectClose(MSXMLHTTP)

 

td:
Can't offer much constructive help nor whether or not it is expected.  But if you are using the same version of both products then you are using exactly the same interpreter in both cases.  This would lead one to believe that the difference in behavior is environmental.   Don't know what that difference might be but you could consider some of the usual suspects like the account running the script, etc.

JTaylor:
Do you have an easy way to test this on WebBatch if I send you a URL directly?  I'm not sure what else to check.  I would think if it were an account issue that it would be blocking on the Object creation as opposed to the Send but you know far more than I.   Not sure what I would change on the account to affect such a thing.

Jim

td:
Don't see why object creation would be blocked simply because of of the objects method's encounters some kind of security issue. 

Presumably, you are dealing with a Web server not of your own creation and you may simply be bumping up against some built in protocol blocking used to prevent  server side exploits or something.  The server wouldn't care about COM objects but might flag simultaneously mixing  open and secured ports on a single worker thread.   Again, this notion is pure speculation on my part and there may be obvious counter examples that show this to not be the case but you might consider searching for information centered around the internals of your Web server software.   

JTaylor:
I have been searching for hours and is why I posted the question since I was going nowhere.   Probably is security related but not sure what to do to fix it.   The certificate on my server is good but not sure how much that comes into play.  I have no control over the other server.    Of course, my ignorance about what MSXMLHTTP is doing with such thing as SSL vs TLS doesn't help.   Not sure if that is coming into play or not and if making sure SSL is disabled on my server would make a difference or not.  Oh well, thought I would ask and hope for the best.

Jim

Navigation

[0] Message Index

[#] Next page

Go to full version