Skip to main content
ViaVu
Level 2
August 26, 2026
Solved

Dispatcher filter rule to allow DELETE method is not working on AEMaaCS

  • August 26, 2026
  • 4 replies
  • 60 views

Hi, I have a Dispatcher filter rule to allow for DELETE method for a specific url path. 

It works fine on my local AEM instance Dispatcher. The same errors out “406 Not Acceptable”

Can you please suggest a fix for the AEMaaCS environment?

The following is how the rule looks in the sites_filters.any file.

/0123 { /type "allow" /method "DELETE" /url "/service/xyz.json”

 

Best answer by Raja_Reddy

Hi , If the DELETE filter works locally but returns 406 on AEMaaCS, I would first verify whether the request is being blocked by Dispatcher, CSRF protection, or another filter in the publish tier. Ensure the DELETE rule is included in the active farm and that no preceding deny rule matches the request. Also check whether a valid CSRF token is required for the DELETE request in AEMaaCS. Reviewing Dispatcher and Publish logs should help identify where the 406 response is being generated.
 

  • Whether the request is reaching Dispatcher or being blocked by AEM/Apache.
  • If a broader deny rule is matching before the allow rule.
  • Whether the endpoint requires a valid CSRF token for DELETE requests.
  • That the filter file is included in the active farm configuration deployed to AEMaaCS.

 

4 replies

ViaVuAuthor
Level 2
August 27, 2026

After troubleshooting AEMaaCS dev environment, it was identified that the CDN was not allowing DELETE operation.

    JayVy4
    Level 2
    September 5, 2026

    Hi ​@ViaVu ,

    Can you help me to understand in more detail what you are trying to fix or delete? Like, is it internal AEM application data or 3rd party data?

    Right now, from limited data, what I'm thinking of is doing the servlet post call to the custom endpoint and internally performing delete operations

    EG: POST /service/xyz.json?action=delete or POST /service/xyz/delete
    /0123 { /type "allow" /method "POST" /url "/service/xyz/delete" }

    Raja_Reddy
    Community Advisor
    Raja_ReddyCommunity AdvisorAccepted solution
    Community Advisor
    September 10, 2026

    Hi , If the DELETE filter works locally but returns 406 on AEMaaCS, I would first verify whether the request is being blocked by Dispatcher, CSRF protection, or another filter in the publish tier. Ensure the DELETE rule is included in the active farm and that no preceding deny rule matches the request. Also check whether a valid CSRF token is required for the DELETE request in AEMaaCS. Reviewing Dispatcher and Publish logs should help identify where the 406 response is being generated.
     

    • Whether the request is reaching Dispatcher or being blocked by AEM/Apache.
    • If a broader deny rule is matching before the allow rule.
    • Whether the endpoint requires a valid CSRF token for DELETE requests.
    • That the filter file is included in the active farm configuration deployed to AEMaaCS.

     

    ViaVuAuthor
    Level 2
    September 10, 2026

    Hi ​@JayVy4 and ​@Raja_Reddy thank you for your responses. I updated this post as resolved 14 days ago with the details. However, it is still showing as unsolved. I’ll see if I can somehow mark it as resolved.  

      Terms & ConditionsAccessibility statement

      Loading footer...