Hello,

We are using the HTTP transaction sensor to verify that our externally facing sites are up. I am getting the error: "URL # 3: Read timed out." once I get to the url that requires for data. How does PRTG like the POST data to be formatted in order to handle these requests?

Below are some examples of requests I have tried to send through--

{
    "Accountnumber": "XXX",
    "Date": "XXX",
    "CVV2": "XXX",
    "Email": "XXX",
    "IsActive": true,
    "FullName": "XXX",
    "ZIP": "XXX",
}

ctl00$DefaultContent$ucSaleInformation$txtAccountNo.AccountNumber=xxx&ctl00$DefaultContent$ucSaleInformation$drpExpirationDateMonth=xxx&ctl00$DefaultContent$ucSaleInformation$drpExpirationDateYear=xxx&ctl00$DefaultContent$ucSaleInformation$txtCVV=xxx&ctl00$DefaultContent$ucAccountHolderInformation$txtAddressLine1.Address1=xxx&ctl00$DefaultContent$ucAccountHolderInformation$txtPostalCode.ZipCode=xxx&ctl00_DefaultContent_btnVerify=True

Article Comments

Usually like that: 

POST /path/ HTTP/1.0
From: frog@jmarshall.com
User-Agent: PRTG/1.0
Content-Type: application/x-www-form-urlencoded
Content-Length: 32

Accountnumber=XXX&Date=XXX&CVV2=XXX&Email=mail@mail.com&IsActive=true&FullName=Test Me"&zip=01395

Make sure that the content-length number matches the length of the last line :)


Jun, 2016 - Permalink

Thank you, Stephan! This helped perfectly.


Aug, 2016 - Permalink

Well that took some time :D Nice that it worked out :)


Aug, 2016 - Permalink