SiteScope 10.10 – URL monitor against SAP portal fails with HTTP 400 Bad Request

New installation of SiteScope 10.10 on Windows 2003

old – still avtive – instance of SiteScope on Windows 2003

URL monitoring to a SAP portal. There are a lot of so called nodes (services) with different URL. One request is working:;saplb_*=203283651

The other one doesn’t work:;saplb_*=3260050

Both are URL content monitors with the same attributes (I copied one from another).

The failing monitors respond with HTTP 400 Bad Request

Enabling DEBUG logging doesn’t reveal anything really useful:

failing with HTTP status 400

2010-08-03 16:25:16,312 [Node 651(CONS/1) ] ( DEBUG – enter HttpState.addCookies(Cookie[])


2010-08-03 16:25:17,078 [Node 651(CONS/1) ] ( DEBUG – alertDebug: f3d9e34 ALERT/GOOD/WARNING/ERROR VALUES: status(value: 400) != 200

succeeding with HTTP Status 200:

2010-08-03 16:26:18,203 [Node 250(PROD.1/2) ] ( DEBUG – enter HttpState.addCookies(Cookie[])


2010-08-03 16:26:18,578 [Node 250(PROD.1/2) ] ( DEBUG – alertDebug: 06de5f4 ALERT/GOOD/WARNING/ERROR VALUES: status(value: 200) != 200

R&D found out that it’s a user-agent issue.

For example you can check this thread :

By default SiteScope uses "User-Agent: Mozilla/4.0 (compatible; MSIE 4.01; Windows NT)" (you can check it in the logs)

To Fix this issue, use "POST data" field (put one of the strings that described below) in URL Content & URL Sequence Monitors(in url sequence step form).

Try to use these :

"User-Agent: Mozilla/4.0"

"User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)"

"User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; YPC 3.0.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)"

"User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9) Gecko/2008052906 Firefox/3.0"

"User-Agent: Opera/9.0 (Windows NT 5.1; U; en)"

"User-Agent: Opera/10.00 (Windows NT 6.0; U; en) Presto/2.2.0"

Try to change it and don’t forget to check it in RunMonitor logs :

User-Agent: Mozilla/4.0 (compatible; MSIE 4.01; Windows NT)

Pragma: No-Cache

Accept: */*




HTTP/1.1 200 OK

Server: SAP J2EE Engine/6.20

Content-Type: text/html; charset=UTF-8

Content-Language: en-US

expires: 0

Date: Fri, 17 Sep 2010 09:29:52 GMT

Transfer-Encoding: chunked

Set-Cookie: sapj2ee_*=1120943600; Version=1; Path=/

Set-Cookie: JSESSIONID=(itnts2221_FCM_00)ID1120943600DB0.6216552420769629End; Version=1;; Path=/


The customer took the liberty to change the User-Agent information in the master.config file to avoid the need to perform this change on each and every monitor.

Changing the user agent solved the problem.

Leave a Comment