Bobcares

HAProxy ACL based on Hostname

by | Dec 8, 2023

Learn more about HAProxy ACL based on hostname. Our HAProxy Support team is here to help you with your questions and concerns.

HAProxy ACL based on hostname

Access Control Lists in HAProxy let us shape traffic flow based on various criteria, offering control over our application’s routing.

HAProxy ACL based on hostname

Today, we are going to take a closer look at a powerful use case of HAProxy ACLs—host-based routing.

Understanding HAProxy ACLs

HAProxy ACLs act as a set of rules defining conditions for processing incoming requests. Furthermore, these rules are key when making decisions about how to route or handle requests, providing flexibility and control over our application’s traffic.

Hostname as a Criterion

One common use of ACLs in HAProxy is routing traffic based on the hostname in the HTTP request. This is often called “host-based routing”. So, it lets us direct requests to different backend servers based on the domain requested.

Configuring ACLs for Hostname Matching

In our HAProxy configuration file, ACLs are defined using the `acl` keyword.

Furthermore, for hostname-based ACLs, the `hdr` (header) or `hdr_dom` (domain) options are used.

acl acl_example hdr(host) -i example.com

So, the ACL named `acl_example` checks if the Host header in the HTTP request matches “example.com.”

Using ACLs in Configuration

Also, after defining ACLs, we can integrate them into our backend or frontend configuration to influence routing decisions.

use_backend example_backend if acl_example

This line tells HAProxy to route traffic to the `example_backend` if the condition specified in the ACL `acl_example` is true.

Consider the following simplified HAProxy configuration demonstrating hostname-based ACLs:

HAProxy ACL based on hostname

Hence, requests with the hostname “example.com” are directed to `example_backend`, while requests with the hostname “anotherdomain.com” are directed to `another_backend`.

Wildcard Matching

HAProxy also supports wildcard matching. So, this enables us to match multiple subdomains with a single ACL. For instance:

acl is_subdomain hdr(host) -i subdomain.*

So, this ACL would match any subdomain under “subdomain.”

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

Conclusion

Today, our Support Engineers introduced us to HAProxy ACL based on hostname.

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