Configuration Section Basics

An HAProxy Enterprise configuration is composed of named sections that differ in what they do. For example, a frontend section receives incoming traffic, a backend section defines a pool of servers that respond to requests, and a mailers section configures where to send email alerts.

Overview

Get an overview of how an HAProxy Enterprise configuration is composed.

Global

Define process-level directives and global configuration settings.

Frontend

Accept incoming connections and forward them to defined backends.

Backend

Define server pools to service incoming requests.

Listen

Define a complete proxy with the functions of a frontend and backend combined.

Defaults

Set inheritable directive defaults for other sections.

Userlist

Configure authentication and restrict access to proxied services.

Cache

Enable in-memory response caching for backend servers.

Http-errors

Configure custom error pages to return to clients.

Mailers

Define message transfer agent (MTA) servers to forward error messages.

Resolvers

Add DNS nameservers to resolve hostnames.

Fcgi-app

Define how HAProxy Enterprise should connect to a FastCGI application.

Peers

Enable the replication of stick table data between HAProxy Enterprise nodes.

Aggregations

Combine stick table data from multiple HAProxy Enterprise nodes.

Program

Enable the HAProxy Process Manager to start external programs.

Dynamic-update

Pull updated ACL and Map files from a remote server.

Log-forward

Configure a syslog listener over UDP or TCP.

Ring

Create an in-memory buffer for log messages before forwarding them to a remote log server.

Next up