Skip to main content
ViaVu
Level 2
Aug 26, 2026 6:08 PM UTC
Solved

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

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”

 

Raja_Reddy
Raja_ReddyAccepted solution
Community Advisor
Sep 10, 2026 4:36 PM UTC

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.

 

View in thread

4 replies

ViaVuAuthor
Level 2
Aug 27, 2026 2:00 AM UTC

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

Translate
    JayVy4
    Level 2
    Sep 5, 2026 12:38 PM UTC

    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" }

    Translate
    Raja_Reddy
    Community Advisor
    Raja_ReddyCommunity AdvisorAccepted solution
    Community Advisor
    Sep 10, 2026 4:36 PM UTC

    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.

     

    Translate
    ViaVuAuthor
    Level 2
    Sep 10, 2026 7:06 PM UTC

    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.  

    Translate
      Terms & ConditionsAccessibility statement

      Loading footer...