This conversation has been locked due to inactivity. Please create a new post.
This conversation has been locked due to inactivity. Please create a new post.
I have enabled the extensions in filters too.
/0010 { /type "allow" /extension '(css|eot|gif|ico|jpeg|jpg|js|gif|pdf|png|svg|swf|ttf|woff|woff2|html|pptx|docx)' /path "/content/*" }
I am able to access the other extensions too but not these. These extensions are working on author and publish but not on dispatcher, any thoughts here?
Thank you.
Solved! Go to Solution.
Views
Replies
Total Likes
@arunpatidar @Shashi_Mulugu , thank you for replying.
the issue was with symbolic links, I have resolved it now.
No @arunpatidar, there aren't any deny rule regarding those extensions.
only deny rules after that are the following:
# Deny content grabbing for greedy queries and prevent un-intended self DOS attacks
/0017 { /type "deny" /selectors '(feed|rss|pages|languages|blueprint|infinity|tidy|sysview|docview|query|[0-9-]+|jcr:content)' /extension '(json|xml|html|feed)' }
# Deny authoring query params
/0018 { /type "deny" /method "GET" /query "debug=*" }
/0019 { /type "deny" /method "GET" /query "wcmmode=*" }
I tried changing the rule id but no luck.
@B_Sravan I have seen your replies to Arun. Can you check if filter which is getting execcuted for the first case, in multiple scenarios, if we have multiple publish farms and in that the filters can be of different paths, and depends on the Publish farm it gets executed for that request, you have to follow thru the same the filter configuration.
Hardway is You can try by removing couple of extensions which is working and confirm if you are modifying the correct file.
@arunpatidar @Shashi_Mulugu , thank you for replying.
the issue was with symbolic links, I have resolved it now.
Views
Likes
Replies