WHALE ENGINE
Documentation
WHALE ENGINE

Network

[network] configures the TLS policy used by Whale‑E for HTTP(S) requests executed after the strategy has been loaded.

It does not configure the proxy. Proxy settings are configured at process level through HTTPS_PROXY, HTTP_PROXY, NO_PROXY, and their lowercase variants.

If you need a custom CA bundle from process startup, especially for update checks, use WHALEE_CA_BUNDLE. Once the strategy is loaded, this environment variable still takes precedence over ca_bundle_path.

For the broader view of network access, proxy handling, TLS, and updates, see Network and security.

Example

[network]
verify_tls     = true
ca_bundle_path = "C:/certs/whale-e-ca-bundle.pem"

Block parameters

ParameterDescription
verify_tls
 Boolean
 Optional		Enables or disables server certificate verification for HTTP(S) requests executed after the strategy is loaded. When this value is false, the engine no longer validates TLS certificates for those requests.
Default value: true
allow_insecure_tls
 Boolean
 Optional		Explicit acknowledgement required when verify_tls = false. If TLS verification is disabled while allow_insecure_tls stays false, the configuration is rejected.
Default value: false
ca_bundle_path
 Text
 Optional		Absolute path to a custom CA bundle file. The path must be absolute and the file must exist. This key is used only when TLS verification is enabled. If WHALEE_CA_BUNDLE is set, it takes precedence over ca_bundle_path.
Default value: no strategy-level custom CA bundle is forced

Additional notes

When verify_tls = false, Whale‑E requires allow_insecure_tls = true so that disabling TLS verification cannot happen silently in the strategy.

The [network] block is read from the strategy file. It therefore cannot be used to configure the proxy or any network setting that must already be available before the strategy is loaded.

Prev
Cancel All
Next
Close