url_response probe returns '(url)' failed - 47 Number of redirects hit maximum amount
search cancel

url_response probe returns '(url)' failed - 47 Number of redirects hit maximum amount

book

Article ID: 144014

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

The URL response probe returns the error:
'(url)'  : failed "47 Number of redirects hit maximum amount".

Environment

  • Release: DX UIM 20.4 or higher
  • Component: UIM - URL_RESPONSE

Cause

  • url_response probe configuration: When following redirects, libcurl hit the maximum amount.
  • url_response parameters need to be updated as described in the resolution

Resolution

1) 47 is not a threshold but a CURL standard error code, e.g.,

    "CURLE_TOO_MANY_REDIRECTS(47)"

Please refer to the CURL documentation on error codes

libcurl error codes

Too many redirects. When following redirects, libcurl hit the maximum amount. Set your limit with CURLOPT_MAXREDIRS.
Redirects are configured through these parameters/keys in the url_response configuration:

enable_redirect_retry
redirect_retry_count
redirect_retry_delay

or

2) In the url_response probe, set enable_redirect_retry = yes

The alarm message changed to 401, "The requested resource requires user authentication."

For the website in question, this is an expected behavior as it redirects to login.

If required, this error can be avoided by using the e2e_appmon_dev probe to record a transaction, e.g., to access the website and login with the username and password.

Details on the keys:

enable_redirect_retry: yes (it is used for redirect retry for url) 
 
Then the two variables below will be work according to configuration:

redirect_retry_count: <number> (number of retry  of redirect  url)  
redirect_retry_delay: <number> (delay in second  on each  retry  of redirect url)