Redirect user to a friendly message page for 406 Error - Not Acceptable

Hi ​@SwethaBe2,

The 406 is being blocked at the CDN layer before it even reaches AEM, so ACS Commons error handling won’t intercept it, that only covers errors that make it through to the Sling/dispatcher layer.

To serve a friendly page for CDN-blocked requests, you need to handle it in your CDN rules config directly. In AEM Cloud Service you can define an errorPages section in your CDN rules YAML to redirect specific status codes to a static or cached friendly page.

Something like:

kind: CDN
version: '1'
metadata:
  envTypes: [dev, stage, prod]
data:
  errorPages:
    rules:
      - name: handle-406
        when:
          reqStatus: 406
        action:
          type: redirect
          location: /errors/not-acceptable

 

The target page should be published and publicly accessible. This keeps the friendly UX consistent regardless of where in the stack the error originates.