asp.net - Unexpected HTTP Status Codes using WCAT with NTLM -


does know how avoid wcat recording unexpected "401 unauthorized" http status codes when testing web application uses ntlm authentication? example of code using request below:

    request     {     url = "http://server";     authentication = ntlm;     username = "user";     password = "xxxx";     statuscode = 200;     } 

to clarify, script works fine , manage retrieve content when ran against iis7 server ntlm negotiation (i believe) means initial 401 code recorded final 200 code.

this means after test report shows same amount of 401 codes 200 codes, , unfortunately 401s recorded unexpected codes/errors.

i realise similar question 1 asked earlier, 1 asking if there way avoid unexpected status codes.

thanks!

what need (i think) transaction { ... } number of request { ... } elements inside, of expect 401 statuscode:

transaction {     id = "home";     weight = 1000;     request     {         url = "/";         statuscode = 401;         redirect = true;         cookies = true;     }     request     {         url = "/";         statuscode = 401;         authentication = ntlm;         username = "domain\\username";         password = "password";         redirect = true;         cookies = true;     }     request     {         url = "/";         authentication = ntlm;         username = "domain\\username";         password = "password";         statuscode = 200;         redirect = true;         cookies = true;     } } 

Comments

Popular posts from this blog

c# - how to write client side events functions for the combobox items -

exception - Python, pyPdf OCR error: pyPdf.utils.PdfReadError: EOF marker not found -