Normalizing requests

Learn how to normalize requests by transforming them using traffic filter rules in AEM as a Cloud Service.

Why and when to transform requests

Request transformations are useful when you want to normalize incoming traffic and reduce unnecessary variance caused by unneeded query parameters or headers. This technique is commonly used to:

These transformations are typically applied at the CDN layer, especially for AEM Publish tiers that serve public traffic.

Prerequisites

Before proceeding, ensure you’ve completed the required setup as described in the How to set up traffic filter and WAF rules tutorial. Also, you have cloned and deployed the AEM WKND Sites Project to your AEM environment.

Example: Unset query parameters not needed by the application

In this example, you configure a rule that removes all query parameters except search and campaignId to reduce cache fragmentation.

kind: "CDN"
version: "1"
metadata:
  envTypes: ["dev", "stage", "prod"]
data:
  requestTransformations:
    rules:
    # Unset all query parameters except those needed for search and campaignId
    - name: unset-all-query-params-except-those-needed
      when:
        reqProperty: tier
        in: ["publish"]
      actions:
        - type: unset
          queryParamMatch: ^(?!search$|campaignId$).*$