Hi Rick,

>>
What seems odd to me is that there a always a pair of these - one with no username (that, as expected, returns a HTTP 401 code) then one with a valid username (I've edited the real name for security). Don't know why a single call to the webservice generates these two entries but I see that it happens on all my web services that require authentication.
>>

>
That's normal - that's how Windows Auth operates. Authentication is always a server iniated task so the server will prompt for authentication with a header and the client then resends with the authentication information.
>

Interesting - I didn't know it worked that way (well I may have read it but not taken it in <s>). So even tho the SoapClient has the authentication information available it doesn't send it unless requested? But if this is the case then why doesn't the same thing happen during the SoapInit() call ? - there's only one hit then and authentication takes place.

Ha - I think maybe I've answered that myself - in my Init call the authentication detail is included in the URL...

Anyway I guess this isn't relevant to my slowdown which I'm still working on without much (well any) success.

Regards,
Viv