Ah yes no problem:Dispatcher 4.3.1Apache 2.4.35

I'm using the module for Apache 2.4 .

Hello again.Is there an answer regarding the below questions?I'm wondering why a 200 is still returned, is this just the way the dispatcher handles the response in the event of a blocked POST request? Is this even a concern or can it be disregarded?The response body for the POST is the content page ...

Thank you again for the quick responses.wimsymons​ - I do have a global deny set as the first rule in the /filter section:/filter/0001 { /type "deny" /glob "*" }When I noticed the POSTs were returning a 200 status code, I added the following rule (below an allow rule using the GET method for the con...

Hi. Thank you for the reply.I'm running on the latest dispatcher version 4.3.1, but I'm still seeing this issue.Regarding testing tools, I followed the guidelines in the Dispatcher Security Checklist when I initially installed and configured the web server and dispatcher. I'm also regularly monitori...

Hello.When sending POST requests to content URLs in our production environment (AEM 6.3.3.1), I'm able to receive a 200 status response to the client.This is despite the fact that I have the following rule in my dispatcher /filter configuration:/0001 { /type "deny" /method "POST" /url "/content/*" }...