http://user:pass@corp.com:8080 � Mixing HTTPS and HTTP The protocol in the URL (either http:// or https://) should match the actual protocol of your proxy server. The keys http and https in the above example example merely indicate the type of traffic to route, not the protocol of the proxy server itself. Ensure that both keys use the correct protocol based on your proxy server's configuration. 4.1. User guide ssl_verify: corp.crt offline: Offline mode only Filters out all channel URLs that do not use the file:// protocol. The default is False. Example: offline: True Advanced configuration allow_softlinks: Disallow

http://user:pass@corp.com:8080 � Mixing HTTPS and HTTP The protocol in the URL (either http:// or https://) should match the actual protocol of your proxy server. The keys http and https in the above example example merely indicate the type of traffic to route, not the protocol of the proxy server itself. Ensure that both keys use the correct protocol based on your proxy server's configuration. 4.1. User guide ssl_verify: corp.crt offline: Offline mode only Filters out all channel URLs that do not use the file:// protocol. The default is False. Example: offline: True Advanced configuration allow_softlinks: Disallow

http://user:pass@corp.com:8080 � Mixing HTTPS and HTTP The protocol in the URL (either http:// or https://) should match the actual protocol of your proxy server. The keys http and https in the above example example merely indicate the type of traffic to route, not the protocol of the proxy server itself. Ensure that both keys use the correct protocol based on your proxy server's configuration. 4.1. User guide ssl_verify: corp.crt offline: Offline mode only Filters out all channel URLs that do not use the file:// protocol. The default is False. Example: offline: True Advanced configuration allow_softlinks: Disallow

http://user:pass@corp.com:8080 � Mixing HTTPS and HTTP The protocol in the URL (either http:// or https://) should match the actual protocol of your proxy server. The keys http and https in the above example example merely indicate the type of traffic to route, not the protocol of the proxy server itself. Ensure that both keys use the correct protocol based on your proxy server's configuration. 4.1. User guide ssl_verify: corp.crt offline: Offline mode only Filters out all channel URLs that do not use the file:// protocol. The default is False. Example: offline: True Advanced configuration allow_softlinks: Disallow

corp.crt Offline mode only (offline) Filters out all channel URLs that do not use the file:// protocol. The default is False. EXAMPLE: offline: True Advanced configuration • Disallow soft-linking ParameterLoader 2. Each Configuration attribute is a ParameterLoader, which implements the property protocol via __get__. This means that, upon attribute access (e.g. MyConfiguration.string_field), the ParameterLoader modify the Context object! ParameterLoader does not implement the __set__ method of the property protocol, so you can freely override an attribute defined in a Configuration subclass. You might think that

corp.crt Offline mode only (offline) Filters out all channel URLs that do not use the file:// protocol. The default is False. EXAMPLE: offline: True Advanced configuration • Disallow soft-linking ParameterLoader 2. Each Configuration attribute is a ParameterLoader, which implements the property protocol via __get__. This means that, upon attribute access (e.g. MyConfiguration.string_field), the ParameterLoader modify the Context object! ParameterLoader does not implement the __set__ method of the property protocol, so you can freely override an attribute defined in a Configuration subclass. You might think that

corp.crt Offline mode only (offline) Filters out all channel URLs that do not use the file:// protocol. The default is False. EXAMPLE: 1.5. Configuration 21 conda Documentation, Release 4.6.0 offline:

corp.crt Offline mode only (offline) Filters out all channel URLs that do not use the file:// protocol. The default is False. EXAMPLE: 1.5. Configuration 21 conda Documentation, Release 4.6.1 offline:

corp.crt Offline mode only (offline) Filters out all channel URLs that do not use the file:// protocol. The default is False. EXAMPLE: offline: True 56 Chapter 4. Contributors welcome conda, Release ParameterLoader 2. Each Configuration attribute is a ParameterLoader, which implements the property protocol via __get__. This means that, upon attribute access (e.g. MyConfiguration.string_field), the ParameterLoader modify the Context object! ParameterLoader does not implement the __set__ method of the property protocol, so you can freely override an attribute defined in a Configuration subclass. You might think that

corp.crt Offline mode only (offline) Filters out all channel URLs that do not use the file:// protocol. The default is False. EXAMPLE: offline: True Advanced configuration • Disallow soft-linking ParameterLoader 2. Each Configuration attribute is a ParameterLoader, which implements the property protocol via __get__. This means that, upon attribute access (e.g. MyConfiguration.string_field), the ParameterLoader modify the Context object! ParameterLoader does not implement the __set__ method of the property protocol, so you can freely override an attribute defined in a Configuration subclass. You might think that