Is there a way to use HTTP sensor to monitor a URL that has a permanent redirect in place (to ensure it's reaching a valid web page)?

For example: Monitoring the main/advertised URL "https://gmail.com" has a 301 redirect to "https://www.google.com/gmail/" which then has a 302 redirect to "https://mail.google.com/mail" to reach the appropriate page.

I've tried setting up a HTTP basic sensor and HTTP advanced sensor on my main URL, or setting up the URL's in a HTTP transaction sensor - but they fail (at the first step) with either 502 Gateway Timeout or Read Time Out.

Checking the help and other KB questions, it seems the HTTP sensors are only designed to monitor the end/working web page (which I already have working). However I'd like to make sure any redirected URL's to those pages are also working as expected.

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Nope, redirects can't be checked :/ You'll need to use PowerShell (or a language of your taste) and a EXE/Script (Advanced) Sensor to properly monitor sites like that.

Kind regards,
Stephan Linke, Tech Support Team


Aug, 2018 - Permalink