How to control circular redirect detection in outbound remote storage requests

Visit for documentation on Nexus Repository version 2.

The HTTP specification has a note regarding circular redirection detection:

A client SHOULD detect infinite redirection loops, since such loops generate network traffic for each redirection.

By default, Nexus Repository 2 remote storage requests have circular redirect detection enabled. If a single circular redirect is detected, the outbound request will fail.

Nexus Repository 2.11.2 and greater allows some configuration of the circular redirect detection for outbound remote storage requests.

How To Adjust Circular Redirect Detection Per Host

Nexus Repository 2.11.2 and greater can be configured to allow up to a hardcoded 10 circular redirects while requesting a remote file for specific hostnames:

  1. Determine what host names you need to allow circular redirects for. The host names should case-insensitively match the host names configured as part of the remote URL value used in a proxy repository.
  2. Edit ${NEXUS_INSTALL_DIR}/conf/ Add a property on a new line with a comma-separated list of remote hostnames:,
  3. Start or restart Nexus Repository 2 for the list of host names to take effect.

    Nexus Repository 2 will allow up to 10 circular redirects for the specified host names. After 10 redirects to the same location, Nexus Repository 2 will fail the outbound request.

Have more questions? Submit a request


Article is closed for comments.