Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Having an issue with HTTP monitor and the Search String function

We are monitoring a website that is https. I have set the port to 443 and the URL to http://naznet.naz.edu. The site monitors fine... unless I add a Search String. Then no matter what the search string is the HTTP monitor will fail.

I tried various things like the port being 80 and the URL being https, but so far no luck. Any string at all in the search box and the monitor fails.

Does anyone have any ideas?

Find more posts tagged with

Accepted answers

aLTeReGo

The reason why the content match is failing is because there's a javascript validation on the page and the HTTP User Experience Monitor in SAM doesn't support Java Script. This is something you should be looking at our Synthetic End User Monitor to monitor as it fully supports Java Script.

JavaScript Disabled Firefox.png

JavaScript Disabled naznet.png

All comments

netlogix

try changing your agent string - I have web sites that send back a different response based on the agent string. I figured that out by doing a packet capture on the monitor and pulling the html page out of the tcpdump (not sure if you have that skill set at you disposal) or you could use linux's wget and specify the search string in that, or a powershell script. Or you could just pop your agent string in there and try it.

RobFredette

Thanks... but the agent string did not make much difference. I had tried that earlier - with the default, with Mozilla/5, with Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20100101 Firefox/11.0. None of them made a difference

I like the idea of trying a packet capture, I may give that a try. My gut is telling me that the issue is something with the SSL, but I am not sure what.

netlogix

Oh, SSL? well tcpdump isn't gonna be very nice and I know wireshark *can* decode if you have the public and private key, but that isn't fun. With SSL I would setup fiddler and set that as the proxy (man-in-the-middle).

aLTeReGo

JavaScript Disabled Firefox.png

JavaScript Disabled naznet.png