Hi @sathishreddy  The reasons for allowing flexibility to allow clientlibs from /etc to /apps is given in the adobe documentation itself. Refer https://docs.adobe.com/content/help/en/experience-manager-65/developing/introduction/clientlibs.html#locating-a-client-library-folder-and-using-the-proxy-cl...

@chintan97patel  did you try out the filter rules?

Hope this helps!

Hi @samaryadav  when you say "pathfield", do you mean the pathfield in the dialog or some other pathfield popup on consoles? Thanks,Nupur   

Hi @v1101  In the similar way, you can send one key value pair with value equals to clientlib category to the JSP include.

@santhosh_kumark  can you elaborate more on your usecase? Are you talking about creating dropdown in component dialog? Thanks!Nupur

Hi @v1101  In order to pass values to JSP, you are in right direction to use requestAttributes. But the parameter requestAttributes takes a map instead of a single value. In order to set a map and then pass as request parameter refer https://docs.adobe.com/content/help/en/experience-manager-htl/usin...

Hi @Mayankg1  First try to understand what constitutes of AEM like Sling, OSGI, JCR, JAVA and try to create your understanding around these.https://docs.adobe.com/content/help/en/experience-manager-learn/cloud-service/underlying-technology/introduction-architecture.html There are good adobe document...

Hi @Shubham_borole  For your case, you can use SDI with "JSI" include type. JSI means it is javascript based sling dynamic include. It will make a call to required header/footer html from clientside means neither akamai not dispatcher has to  resolve these includes.Both Header/Footer node request HT...

Hi The scenario you mentioned is really one out of 100 scenario. You have done both the requirments to achieve this i.e Enabling Encapsulated token support and User Syncing. If you really want your setup to work 100%, you can go next with Dispatcher sticky session along with above you points. Dispat...