How to configure a proxy repository to

Why does proxying require special configuration?

Oracle requires a complicated interaction that involves authentication, large numbers of HTTP redirects and session cookies for a single content download. These requirements are not typical of other remote URLs you might usually proxy.

More information about Oracle's Maven repository is at

Nexus 3.2.1 and greater

Nexus 3.2.1 and greater can proxy

Proxying requires special HTTP options:

  • Enable circular redirects must be checked
  • Enable cookies must be checked.
  • Valid Oracle authentication credentials must be entered for the proxy repository

By enabling these options, you allow the repository manager to maintain the authentication state in a cookie that would be sent with each request, limiting the need for authentication-related redirects and avoiding timeouts.

Nexus 3.0.0 to 3.2.0 versions

Nexus 3.0.0 to 3.2.0 versions do not have support for proxying

Nexus 2 versions 2.11.2 and greater

Nexus 2 versions 2.11.2 and greater can be configured to use a Maven 2 Proxy Repository to

  1. Edit ${NEXUS_INSTALL_DIR}/conf/, by adding these lines:
    # Comma separated list of hostnames that needs to accept circular redirections
    # Comma separated list of hostnames that benefit from using cookies
  2. Start or restart Nexus to pick up the changes
  3. Create an Oracle Maven 2 proxy repository using as the remote URL. Enter your Oracle credentials into the Authentication section of the repository configuration.

Nexus 2.x Browse Remote does not work with the Oracle repository. Oracle does not support browsing the directory listing of their repository. [NEXUS-8272]

Have more questions? Submit a request


Article is closed for comments.