Yes I agree. Thats why in my first answer, I suggested to remove this configuration temporarily to check whether the request is indeed blocked by CSRF or not. The ideal solution is to include the CSRF javascript on the form page which passes the token along with the form data. 

Hi Samir, Yes, that is what I meant. You do not need to create the mycomponent in apps as you have already registered this resource type by binding it to the servlet. When you access any page which has this sling:resourceType then Sling will call the servlet automatically. You can restrict access to...

Also,  instead of checking the checkbox in the CSRF configuration you should just remove the POST string from the Filter methods by clicking on the minus button.  

Do you see any errors in the error.log file when you submit the form ?

If you are on 6.1 version then I think the POST request is being blocked by the CSRF filter. And to resolve this you should include the CSRF javascript on the page which will automatically inject the CSRF token parameter in your form before submitting it.  You can confirm whether this request is blo...

Try the following regex pattern for this use case- /content/www/(?!(dir1)|(dir2)).*

I guess you need to add new domain of your dispatcher in the externalizer configuration of your author to solve this error- http://localhost:4502/system/console/configMgr/com.day.cq.commons.impl.ExternalizerImpl

The error you now see is because of the limitation of the obfuscated uber jar file. The obfuscated file was created so that you can compile your code by just adding one dependency in your pom file. However, since it is obfuscated it does not have the full implementation code but only a skeleton code...

On 6.1 , you should only add the uber-jar as a dependency in your pom as the ecommerce API is included within uber-jar. Remove the com.adobe.cq.commerce dependency from your pom file and rebuild again. 

I think it will work as the reporting query framework does post processing/filtering on the result set returned by just doing a simple query rather than adding the predicate conditions to the query itself for filtering. You can check the out of the box page audit report for checking the performance ...