Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: XMLHTTP and proxy authentication

From: "jayderk" <jayderk@-------.--->
To: NULL
Date: 6/10/2004 8:14:00 AM
Hello.

Chad I was just wondering if you got a response for your question?

I have had a post out there for 20 days about proxy with no response so I
will ask this question.
is there any reason why they would not include proxy server configuration in
MSXML 4.0 Client Send ?

    xmlCon As New MSXML2.XMLHTTP40
    xmlCon.open "POST", HostServer, False
    xmlCon.send xmldoc.XML

in this code I would think they would include something like
    xmlCon.proxySettings = "port:80,pass=test1" 'or something to that effect




"chad" <anonymous@d...> wrote in message
news:0FC3B204-DC34-4670-BA18-08F7F3700279@m......
> Is any "extra work" required to handle digest, basic, NTLM authentication
against proxies in general if using IXMLHttpRequest in MSXML2?
>
> It seems like we had to write extra code when using WinInet to handle a
challenge response when a connection was opened on the server (when a proxy
required authentication). WinInet had functions for prompting the user for
their credentials (for basic and digest authentication). The keep-alive
header had to be set for NTLM authentication.
>
> Do we need to do anything extra if we use XMLHTTP?
>
> If it does handle it automagically, then how does XMLHTTP keep the
credentials around for subsequent HTTP posts? Or does it prompt the user
every time you make an HTTP request?
>
>
> Thanks in advance for any help,
>
>
> Chad




transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent