cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

URL Monitor with 403 (Forbidden) Redirect.

JamesKitson
Dynatrace Leader
Dynatrace Leader

Hello,

We ran into a minor issue where a url monitor is getting a 403 and redirecting to a different page, but the return code in the monitor is only returning that 403. Is there anyway to use avoid this and return only the final return code (I'm not sure if the monitor is redirecting or just stopping at the first request)? We can set up individual monitors to the page they are redirected to but the way it is at present greatly simplifies the configuration and incident creation.

The configuration of the plugin lets you set a max number of redirects so it seems like it supposed to be able to handle this (Edit - looks like only the standard redirect codes will use this - 301 - 303,307)

Any ideas will help,

James

4 REPLIES 4

gabriel_casella
Dynatrace Pro
Dynatrace Pro

Can you set the plugin's log level to FINER and then see what happens in the log during this execution!?

Maybe the plugin is only programmed to deal with the standard redirect codes that you told above.

JamesKitson
Dynatrace Leader
Dynatrace Leader

Ah, never updated here. It is the case that it will only follow redirects using 'standard' redirect codes. It says it in the details for the allowed number of redirects field in the plugin configuration. So it seems like a modification of the plugin is the only route to get this behavior and since this is a Dynatrace supported plugin any changes would get wiped out in the case that we upgraded. Since this use case was somewhat minor we have gone with the workaround of monitoring the last endpoint directly and dealing with the slight complexity increase that comes with it.

Would this be an opportunity of stating that the application should be using standard redirect protocols in this case?! (Even though it's forbidden the main is the redirection). Tks

Probably, but it's a small config management tool that we're just making sure is up by checking the login interface and I don't believe the owners would know or want to devote time to resolving this just for this. We talked with them briefly about this and decided to just monitor the last url.