Difference between revisions of "Forward Proxy"
Jump to navigation
Jump to search
(→Connection Errors) |
(→How to Create) |
||
| Line 5: | Line 5: | ||
This feature allows particular requests to be passed to a particular proxy. | This feature allows particular requests to be passed to a particular proxy. | ||
| − | == | + | == Specifying a Proxy == |
| + | Forward Proxies can be specified on the settings page: Server Settings -> Forward Proxies | ||
| + | A proxy is defined by: | ||
| + | * The Domain to use the proxies for. A Domain may have wildcards specified by an asterisk (*). E.g. *.sdmx.org | ||
| + | * The host of the proxy to use | ||
| + | * The port of the proxy | ||
| + | * The user ID to use for authentication on the proxy - this is optional. | ||
| + | * The password to use for authentication on the proxy - this is optional. | ||
| + | |||
| + | '''Note:''' Do not specify http or https when specifying either the domain or proxy | ||
== Troubleshooting == | == Troubleshooting == | ||
Revision as of 01:18, 2 November 2021
Overview
From Fusion Registry 10.8.0 onwards a new feature has been added to the Fusion Registry: HTTP Forward Proxies.
This feature allows particular requests to be passed to a particular proxy.
Specifying a Proxy
Forward Proxies can be specified on the settings page: Server Settings -> Forward Proxies
A proxy is defined by:
- The Domain to use the proxies for. A Domain may have wildcards specified by an asterisk (*). E.g. *.sdmx.org
- The host of the proxy to use
- The port of the proxy
- The user ID to use for authentication on the proxy - this is optional.
- The password to use for authentication on the proxy - this is optional.
Note: Do not specify http or https when specifying either the domain or proxy
Troubleshooting
Error #1
Registry reports:
Can not make connection to URL: <<< a url >>> Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Authentication Required"
Possible causes:
- Your authentication has not been specified or has been specified incorrectly.
- The tunnelling needs to disable BASIC authentication. Apply the following to your Java environment and restart the Registry:
-Djdk.http.auth.tunneling.disabledSchemes=""
For further information refer to: https://stackoverflow.com/questions/41505219/unable-to-tunnel-through-proxy-proxy-returns-http-1-1-407-via-https
