Skip to content

Squid connector — squid-connector.conf

The connector reads /etc/enforcegate/squid-connector.conf. The default file ships with one engine target (the local engine on 127.0.0.1) and a [redirector] block telling the connector how to parse the QF-3 request line from Squid:

/etc/enforcegate/squid-connector.conf (defaults)
[engine.remote]
net  = "tcp"
host = "127.0.0.1"
port = 11224
key  = "pleasechangethiskey"

[redirector]
request_line_format = 1

The key value must exactly match the engine's [connectors.local].key (see Engine configuration). The generate-engine-key boot one-shot does this automatically on first boot — for the default standalone deployment shape no operator action is required.

For the complete configuration-attribute schema (every TOML key, default, and type), see the Squid connector reference.

Pointing the connector at a remote engine

For a standalone Squid deployment on a separate host that forwards to a remote EnforceGate engine, edit [engine.remote].host to the engine's reachable address (and port if you've changed the Defendr listener), then set key to match the corresponding entry the engine has under [connectors.<name>].key:

[engine.remote]
net  = "tcp"
host = "engine.example.internal"
port = 11224
key  = "abcdef1234567890"

Drop the matching enforcegate-squid-connector binary on that host as a url_rewrite_program helper — see the Squid connector reference for the squid.conf stanza.