Proxy Servers

As of Cronicle v0.9.82, proxies are supported for both outgoing web hook requests, and the HTTP Plugin.

To send requests through a proxy, simply set one or more of the de-facto standard environment variables used for this purpose:

HTTPS_PROXY
HTTP_PROXY
ALL_PROXY
NO_PROXY

Cronicle will detect these environment variables and automatically configure proxy routing for outbound requests. The environment variable names may be upper or lower-case. The proxy format should be a fully-qualified URL with port number. To set a single proxy server for handling both HTTP and HTTPS requests, the simplest way is to just set ALL_PROXY (usually specified via a plain HTTP URL with port). Example:

ALL_PROXY=http://company-proxy-server.com:8080

Use the NO_PROXY environment variable to specify a comma-separated domain whitelist. Requests to any of the domains on this list will bypass the proxy and be sent directly. Example:

NO_PROXY=direct.example.com

Please note that for proxying HTTPS (SSL) requests, unless you have pre-configured your client machine to trust your proxy's local SSL cert, you will have to set the rejectUnauthorized option to false in your requests. For web hook requests, set this in the web_hook_custom_opts configuration object:

"web_hook_custom_opts": {
	"rejectUnauthorized": false
}

Similarly, for using the HTTP Plugin, you may need to check the "SSL Cert Bypass" checkbox.

The types of proxies supported in Cronicle are:

Protocol	Example
http	http://proxy-server-over-tcp.com:3128
https	https://proxy-server-over-tls.com:3129
socks	socks://username:[email protected]:9050
socks5	socks5://username:[email protected]:9050
socks4	socks4://some-socks-proxy.com:9050
pac-*	pac+http://www.example.com/proxy.pac