I am using a low level SOAP approach and I am having a weird behavior with the EndPointUrl property. I discovered this when I started to get "No matching authorization scheme enable on connector".

I am using something like this:

Connector.Property("EndPointURL")="https://myusername:mypassword@www.myweb.com/mydir/mydir2/mydir3/mydir4/MyFile.asmx"

When using that approach, I get the above message. When I do this:

Connector.Property("EndPointURL")="https://myusername:mypassword@www.myweb.com/mydirbad/mydir2/mydir3/mydir4/MyFile.asmx"

I get: "Unknown COM status code".

But, when I call using a bad directory on the following directories, I always get the first message. So, the following calls would give me "No matching authorization scheme enable on connector".

Connector.Property("EndPointURL")="https://myusername:mypassword@www.myweb.com/mydir/mydir2bad/mydir3/mydir4/MyFile.asmx"
Connector.Property("EndPointURL")="https://myusername:mypassword@www.myweb.com/mydir/mydir2/mydir3bad/mydir4/MyFile.asmx"
Connector.Property("EndPointURL")="https://myusername:mypassword@www.myweb.com/mydir/mydir2/mydir3/mydir4bad/MyFile.asmx"
Connector.Property("EndPointURL")="https://myusername:mypassword@www.myweb.com/mydir/mydir2/mydir3/mydir4/MyFileBad.asmx"

So, can anyone explain me the brilliant logic behind all this? Why is the first call to a bad directory giving me the "Unknown COM status code" but other bad directory calls would give me the "No matching authorization scheme enable on connector"?