Solved! Go to Solution.
XSS is not something dispatcher can protect you against in general. XSS protection must be built into the code which produces the output being returned in response to requests from the users browser. E.g. in JSPs the XSSAPI (https://docs.adobe.com/docs/en/cq/5-6-1/javadoc/com/adobe/granite/xss/XSSAPI.html) should be used to filter or encode any values being included in the output if they come from the request, the JCR, or any external data source.
-Rob
Using Sightly will automatically XSS-protect all your output
Views
Replies
Total Likes
I am using CQ 5.6.1 without Sightly ,do you have any links or code sinppet as what I could add in dispatcher section that could protect from XSS ,which in general could be used to protect the website from XSS
Views
Replies
Total Likes
XSS is not something dispatcher can protect you against in general. XSS protection must be built into the code which produces the output being returned in response to requests from the users browser. E.g. in JSPs the XSSAPI (https://docs.adobe.com/docs/en/cq/5-6-1/javadoc/com/adobe/granite/xss/XSSAPI.html) should be used to filter or encode any values being included in the output if they come from the request, the JCR, or any external data source.
-Rob
See this AEM topic:
https://docs.adobe.com/docs/en/cq/5-6-1/developing/developing_guidelines_bestpractices.html#Protect against Cross-Site Scripting (XSS)
Views
Replies
Total Likes
Hi @chandra_cq5
I am also facing the same issue, did you got any solution.? I am trying to make the changes at code level but not able to figure out how to implement XSSAPI.
If you have done the changes please let me know.
Views
Replies
Total Likes
Views
Likes
Replies