The web monitor follows redirections, making it impossible to monitor, for example, a 302 status code. Here is a use case:

We have an application that required https. http://myapp/* redirects to https://myapp/*. I want to be able to set up a scenario step that checks http://myapp/ and gets a redirect status code (302) to ensure that my apache redirect/rewrite is in place.

I understand that this may not be the "usual" behavior that most people would want (to not follow the redirection), but I believe it should be an option to configure whether or not CURLOPT_FOLLOWLOCATION is set. If I have some time – no promises there – I may look into rolling a patch.

(reference httptest.c:311)