


Hi,
I'm working with AEM Forms in AEM 6.5.8 and at the time of submiting a form, the forms trigger requests with jcr:content instead of _jcr_content
POST /content/forms/af/.../jcr:content/guideContainer.af.internalsubmit.jsp
POST /content/forms/af/.../jcr:content/guideContainer.af.submit.jsp
These requests are causing issues since jcr:content is not allowed in the WAF rules.
Namespace Mangling in the Apache Sling Resource Resolver Factory is enabled. We found that the file that is creating these requests is GuideBridge.js
Does anyone know if there's a configuration missing?
Thanks in advance
Juan
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Sign in to like this content
Total Likes
Are you submitting the form to a servlet? OOTB form submission will trigger requests with jcr:content only:
POST /content/forms/af/.../jcr:content/guideContainer.af.internalsubmit.jsp
POST /content/forms/af/.../jcr:content/guideContainer.af.submit.jsp
Namespace mangling [0] is enabled by default so configuration shouldn't be an issue. Are you using dispatcher with the set-up? Or is it not working OOTB? Please elaborate the use-case.
@juanrafaelmaldo This is working as expected. The request go to the submit handler via jcr:content only.