:setenv=http_proxy=http\c//proxy.example\c8080,https_proxy=http\c//proxy.example\c8080:

Merge this field into the appropriate existing login-class record in /etc/login.conf, using an HTTP endpoint from your service or the HTTP proxy list and preserving the class's other required setenv entries.

The file's colons separate capability fields. FreeBSD's \c escape puts a literal colon inside a value, so the receiving environment gets an ordinary URL such as http://proxy.example:8080. Do not copy the capability-file escapes into a client's proxy URL field.

After editing, refresh the capability database with cap_mkdb /etc/login.conf, then establish a fresh login using that class. An existing shell keeps its own environment.

Check the receiving application rather than assuming all services adopted the value. Lowercase http_proxy is intentional here, but clients differ in supported variable names, and login-class environment setup does not configure every daemon.

Artiglyn mynjee