Hi Rick,

I'm trying to run a recorded script on an internal staging site which is only accessible from my corporate network. I get this dialog:

(I have no clue where that pingdom.net URL is coming from.) The dialog indicates this should be placed in the "root of your Web Server". I'm assuming this means the root folder of the site in IIS. Per the dialog, I have tried adding both the allow string in the site's robots file as well as the stand-alone text file but no joy getting the test to run.

Any other suggestions on how I can get WebSurge to run my load test against this internal staging site?

TIA

Not sure, but something's not right if it's pointing at pingdom.net. It sounds like there's some sort of DNS mapping/re-routing going on?

What URls are using for your tests?

Basically to test - you should create a test URL in WebSurge to point at websurge-allow.txt and see what you get. Or try it in the browser if that doesn't work. You should be able to reach that file.

+++ Rick ---

Thanks. Making sure I could hit the websurge-allow.txt file was in the back of my head. 😃

This is the response, I believe.

GET http://staging2.lawson.rfcsystems.com/websurge-allow.txt HTTP/1.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9
Cookie: ASPSESSIONIDQQBASCSR=DBHNADLAANHPPBMAHFADJGNO; __adroll_fpc=17bd59c8b6d372eb71a1f98f60d1ef4c-1674678507546; Lawsons2020=tokenID=428316205; __utma=25578239.1414785053.1674678533.1674678533.1674678533.1; __utmc=25578239; __utmz=25578239.1674678533.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); _fbp=fb.1.1674678533117.1848395564; ASPSESSIONIDCQBQRRQB=BGCHIIMAMHONPHFMMGKBIKJA; ASPSESSIONIDASBQRRQB=CGCHIIMAALHCLAEGOELGOAMG; Status=Login=FALSE; __ar_v4=4LIHRWLJOVA6JL2CD5KH5U%3A20230124%3A34%7C7LQQB5NYLNDFHIWP27E4U6%3A20230124%3A34%7CMQRCEVNH3RHNLCCHTZ5N5M%3A20230124%3A34
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36 Edg/109.0.1518.61

------------------------------------------------------------------

And that does run as a load test.

I don't know the code for this site very well. I'll check in with my web dev to see if there are some clues as to where those pingdom calls are coming from. I assume I can also disable or remove those URLs from the websurge file.

I ripped all those pingdom URLs out of the WebSurge file using my trusty Ken Levy approved text editor and it's now running.