Block IP

If visitors, crawlers, or spammers are degrading the performance of your site, it may be appropriate to block these from accessing your website content.

Rather than letting these requests be processed by Section and your origin server, you can block them as they enter Section.

There are two approaches to Blocking IP’s.

  1. IP Restrictions screen in Aperture web dashboard
  2. section.config.json in Advanced Config & git workflow

The simplest interface to view/edit these values is available via “Configuration” > “IP Restrictions”.

Note that blocking an IP within Aperture as described above adds the IP to the file section.config.json behind the scenes.

1. Block IP via Aperture IP Restrictions

Requests can be blocked by IP address or routing prefix.

Block IPs

For each requesting IP you wish to block requests from, click the “Add Another” button on the page and enter the address or range that you wish to block to the “IP address/CIDR block” text box. Once complete, press the “Save” button.

Within a few seconds Section will be blocking requests from your blacklist.

2. Manage your IP blacklist from within your application repository

The IP blacklist is stored in the section.config.json file in the root of the git repository for your web site. You can view this by going to, selecting your site and then going to the “Advanced Config” page.

Simple proxy stack

The ip_blacklist field is applied to an environment (living at the same level as origin ). It is a list (array) of IP v4 addresses and/or CIDR notation routing prefixes.

The request blacklist is specified via an ip_blacklist property inside one of the environment objects found within the section.config.json file inside your Advanced Configuration tab of Aperture — for example:

    "proxychain": [],
    "environments": {
        "Production": {
            "origin": {
                "address": ""
            "ip_blacklist": [
        "Development": {
            "origin": {
                "address": ""

The section.config.json file blacklist accepts individual IP addresses as well as entire subnets. This configuration file would block all requests from and from the IP range of The origin server would never even see the requests and the Section platform would deliver 403 forbidden errors directly to the (likely malicious) clients.

If you prefer, you can create a custom response to entities on the IP blacklist.