CDN settings

Content Delivery Network (CDN) settings play a crucial role in optimizing website performance and enhancing user experience during deployment. You want to ensure that only legitimate visitors are able to gain access to certain areas of your site including administrative or internal areas of your site. It’s important to provide an optimal experience for site visitors during peak times and keep the site up and running. The features shown here in CDN settings help to cover you on both fronts.

Access control

With Access control in Magnolia PaaS, you’re able to configure rules that prohibit access to certain paths and extensions. This prevents any unintended visits to pages that should be internal or files that should be kept for certain groups or individuals.

Apply CDN restrictions

View from the Cockpit

access control

  1. Go to Content delivery > CDN Settings.

  2. Go to Access control.

  3. Choose the Cluster Id from the dropdown.

  4. Click Apply Filters.

  5. Click the to create a new restriction.

    1. Enter the Path that you want to protect.

      example
      /internal/* (1)
      1 This would protect all areas of the site under internal.
    2. If desired, enable Path matches the start (^). This ensures that the match occurs only if the URL path starts with the specified pattern.

    3. If desired, add any extensions that you explicitly want to protect under this path. The extensions should be separated by commas.

      example
      pdf,txt,jpg,png
  6. Click Apply CDN restrictions.

Geofencing

Magnolia PaaS’s geofencing lets you control access to your site content based on a user’s geographic location. This allows you to define country boundaries around your site’s access. The feature ensures you’re able to comply with regional regulations, enforce licensing restrictions, or tailor content based on geographic targeting.

Apply Geofencing

View from the Cockpit

geofencing

  1. Go to Content delivery > CDN Settings.

  2. Go to Geofencing.

  3. Click Add rule to add a new geofencing rule.

    1. Select the countries from the menu.

    2. Add the host(s) you want to restrict in the Hosts field.

  4. Click Apply geofencing.

Fastly Waiting Room

Premium feature

The Fastly Waiting Room is a feature to help you manage high traffic volume on your site and prevent site overload. It assigns a delay for new user requests which allows existing users to finish what they’re trying to do.

The Fastly Waiting Room:

  • Prevents site overload by intelligently handling the influx of new visitors.

  • Fairly distributes the site traffic so that each user has equal chance of access. During high-demand events, promotions, or sales, this can be highly useful.

  • Reduces server load so performance is not hindered.

waiting room journey

Get the Fastly Waiting Room

The Fastly Waiting Room is a premium feature. You’ll need to talk with your Magnolia PaaS representative to discuss enabling the feature.

You must have the appropriate admin privileges to enable the Fastly Waiting Room. If you go to the Waiting Room in the Cockpit without the appropriate privileges, you’ll see an error page. If your account has the privileges to enable the Fastly Waiting Room, you can follow the instructions here.

Configure the Fastly Waiting Room

  1. In your Cockpit, go to Content delivery > CDN Settings.

    View from the Cockpit

    waiting room cockpit

  2. Go to Waiting room.

  3. Choose the Cluster Id from the dropdown.

  4. Click Apply Filters.

  5. Toggle Enable Waiting Room to enable the feature.

  6. Input the Wait period duration in seconds.

    This is the minimum period of time a visitor must wait before a decision to grant access is made.

  7. Input the Allow percentage. Enter a value between 0 and 100.

    Important considerations

    • This determines what percentage of new requests are allowed to proceed to the site at any point.

    • It helps to control the traffic in a way that prevents server overload.

    • 0 means no new requests are allowed to enter the site.

    • 100 means all new requests are allowed to enter the site.

    The Default is 50 meaning 50% go to the site and 50% go to the waiting room.

  8. Input the Time in seconds a client is allowed to access.

    This is how long the site visitor can stay on the site after access is granted.

    Default is 3600 seconds (60 minutes/1 hour)

  9. Input Page refresh time in seconds.

    This is how long the Waiting Room waits to refresh and check for cookie status. Default is 5 seconds

  10. Input the HTML that is used to render the look and feel of the Waiting Room.

    Sample and tips

    There is a limit of 8000 characters for the field.

    This is just an example. You should use your own template and design to ensure a seamless look and feel for your users.

    <!DOCTYPE html>
    <html lang="en">
       <head>
          <meta charset="UTF-8">
          <title>Waiting Room</title> (1)
       </head>
       <body>
          <div class="container">
             <h1>Welcome to the Waiting Room</h1> (2)
             <p>We apologize for the inconvenience, but the site is quite busy.</p> (3)
             <p>Enjoy this dancing penguin while you wait.</p> (3)
             <img src="dancing-penguin.jpg" alt="Dancing Penguin funny">
          </div>
       </body>
    </html>
    1 Give the Waiting Room a meaningful title.
    2 Write a thoughtful header.
    3 It’s important to explain what is happening to the user.
Feedback

PaaS

×

Location

This widget lets you know where you are on the docs site.

You are currently perusing through the Magnolia PaaS docs.

Main doc sections

DX Core Headless PaaS Legacy Cloud Incubator modules