Bobcares

HAproxy Backend ACL

by | Apr 4, 2024

Learn how to use HAproxy Backend ACL. Our HAproxy Support team is here to help you with your questions and concerns.

HAproxy Backend ACL

HAProxy plays a huge role when it comes to load balancing and proxying. One of its key features is Access Control Lists (ACLs). It enables administrators to define conditions as per different attributes and make routing decisions or apply specific rules to different types of traffic.

HAproxy Backend ACL

When it comes to HAProxy backends, ACLs play a key role in determining which backend should handle a particular request based on certain conditions. Let’s take a look at how we can use HAProxy backend ACLs to streamline our traffic routing.

  1. The first step in utilizing HAProxy backend ACLs is defining the ACLs. This is done with the `acl` keyword followed by a name and a condition. These conditions can be based on factors like headers, paths, source IP addresses, or any other attributes that HAProxy can inspect.

    acl acl_name condition

    For example, we can create an ACL based on a specific path:

    acl is_blog path_beg /blog

  2. Then, it is time to employt he ACLs to direct traffic to specific backends using the `use_backend` directive. This directive lets us route requests as per the conditions in the ACLs.
    use_backend backend_name if acl_name
    For example, we can route requests to a backend named “blog_backend” if the path begins with “/blog”:

    use_backend blog_backend if is_blog

  3. Now it is time to define the corresponding backends. Backends specify where the traffic should be sent based on the ACL conditions.

    backend backend_name
    mode <mode>
    server server_name server_address:server_port

    For example:

    backend blog_backend
    mode http
    server blog_server_1 192.168.1.10:80
    server blog_server_2 192.168.1.11:80

A Complete Example

Let’s put it all together with this example:

# Define ACL based on the path
acl is_blog path_beg /blog
# Use ACL to route traffic to the appropriate backend
use_backend blog_backend if is_blog
# Define the backend for blog traffic
backend blog_backend
mode http
server blog_server_1 192.168.1.10:80
server blog_server_2 192.168.1.11:80

In this example, requests with paths starting with “/blog” will be directed to the “blog_backend,” while other requests will follow default rules or other ACLs.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Experts demonstrated how to use HAproxy Backend ACL.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF