Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi Katmandu25,
As per the log you shared, it looks like you are trying to access the path with selectors and extensions. I got a similar issue with the servlet registered with the resource type. This might be due to dispatcher rules not being deployed even though execute the full stack pipeline. Add the below rule in the dispatcher farm file( "../filters/001_digital_filters.any") then run the dispatcher pipeline(web tier) and check.
/xxxx { /type "allow" /path "/content/*" /selectors "getpublications" /extension "json"}
We can add a method as well if needed.
Thanks,
SS
Views
Replies
Total Likes
Hi Suresh.
Thank you for your response.
First of all I don´t think so the problem is in filters file, in fact we have the following rules on it
/0075 { /type "deny" /url "/content*" /suffix "*" }
/0076 { /type "deny" /url "/content*" /selectors "*" }
/0077 { /type "allow" /url "/content/digital/*" /selectors "*"}
/0078 { /type "allow" /url "/content/digital/*" /suffix "*"}
/0079 { /type "allow" /url "/content/dam/digital/*" /selectors "*"}
/0080 { /type "allow" /url "/content/dam/digital/*" /suffix "*"}
Even if a I "force" to use the right farm, the website works OK.
If you see the log I shared, I think publishfarm is the key:
I have installed a local dispatcher in my laptop and when I ask for the website in my log I can see the following:
Views
Replies
Total Likes
Hopefully, you found the answer already. If not, try renaming your farm file with the different prefix like zzz_ to zzz_digital.farm, so that it's placed earlier in order than your default publish farm.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies