Is there a way to keep the HTTP Monitor from failing when it sees 403 Forbidden?

We have a web site that requires a login and password. When the user goes to the page, it does an authentication check which returns "403 Forbidden" and then redirects the user to the login page. When the SAM HTTP Monitor sees the 403 Forbidden, SAM flags the site as Down and it never shows it as Up. How can I set the HTTP Monitor to ignore the 403 Forbidden so it can see the login page? Part of a packet capture is attached to show the process. I don't ever see 200 OK. Thanks!

LoginPage.jpg

Find more posts tagged with

403 forbidden

http

web site

Accepted answers

All comments

aLTeReGo

You should configure SAM's HTTP/HTTPS User Experience Monitor to use the URL of the redirected login, rather than the root level URL. Based upon the packet capture image shared, you could also point at '${IP}/shared/images/login.jpg' and that should work.

mkomeara

Still no joy - When I test it still says "The remote server returned an error: (403) Forbidden" Here is the settings dialog for the HTTP Monitor. The login.jpg is sent several packets after the 403 Forbidden, and the monitor doesn't get past the 403.

aLTeReGo

based on the screenshot you posted it appears you placed the URL I referenced into the wrong field. The URL '${IP}/shared/images/login.jpg' should be placed into the URL field rather than the Search String field.

mkomeara

I changed that and it still fails when it sees the 403 packet.