I have everything in just 1 dispatcher.any file and the other filters are working fine so I don't have any reason to believe it's not getting executed on the correct farm.  Plus this does work perfectly fine: /0012 { /type "allow" /url "/etc.clientlibs/clientlibs/*" }

Okay, that makes sense actually.  Because of the dot, it *thinks* clientlibs is an extension.  Let me give that a try.

I can't get filter extension restrictions to work for /etc.clientlibs paths. I'm guessing because it is a proxied path and not a physical path. Is this even possible? Here is my config:     /filter { # Deny everything first and then allow specific entries /0001 { /type "deny" /glob "*" } #This work...

I put it in the /install folder and that worked.  Thank you.  However, I'm going to play around with this a bit more because I have one system with SP11 in the /install folder and then I applied SP12 through the package manager.  productinfo indicates SP12 is running and everything seems to be worki...

What should the process be to upgrade an existing service pack?  I have the SP11 zip sitting in the crx-quickstart/install folder from when I installed it months ago.  I now want to apply SP14.

I am disappointed to see the dispatcher still does not allow for case insensitive extensions.  Or at least on v4.3.3 which is what I am using. @joej47544984   Can you share your regex?  I don't see it in the post above.

Thank you for sharing.  I looked far and wide for this solution and this is the only place I found it.  It's referenced here: https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-16936.html?lang=en.  But that doesn't say anything about the login-token cookie.   In our case, X-F...

I know it's been a while, but I did want to close this out.  Turns out all three properties were related to the same nodes/pages so a single index did indeed work, like you have @DEBAL_DAS.   This is what mine looks like: If you were deploying via package, this is the entry that would go in /jcr_ro...

I know it's been some time, but I did want to follow up on this.  Those SQL queries did indeed work, so thank you @lukasz-m.  I also added rep:Restrictions. They don't line up with the allow/deny results so you have to manually sort them with the correct allow/deny.  DM me if you want the entire pac...

Thank you.  I found that post also but it's quite old so I didn't know if those methods were still valid.