It was so long time ago, I believe I just looped over permissions at the given path and all its parents to collect the data

You cannot cache the touch UI request because otherwise you are not able to use the new version of css or js if you install a new SP or CFP. And you need to delete the generated cache manually after the update of your instance.I don't think it is the case otherwise Classic UI was also mentioned. The...

Good point about security, antoniom54959291​, indeed https is required for SSO integration or authentication flow if handled by directly by author. Does anyone know why Touch UI requests cannot be cached? All content related GET calls have timestamped URL query so they are bypassing cache anyway.

Is there any advantage of having dispatcher in front of the Author if it is the only instance, so load-balancing is not required, and as per official documentation cache should be disabled there anyway?So far it only proxying requests between :80 and :4502 ports to underlying publisher and that's pr...

Tracing com.day.cq.tagging made sense, after digging through a number of messages I found one from com.day.cq.tagging.impl.JcrTagManagerImpl which actually revealed underlying query. For the record, it was:/jcr:root/content/xyz//element(*, cq:Taggable)[ (@cq:tags = 'newsroom:event' or @cq:tags = '/e...

Once again, it's not an isolated query, we are using standard AEM List component so I just don;t know how that query looks like in TagManager implementation and that is exactly what i'm trying figure out in order to be able to tweak indexes appropriately

The point is there is no "my query", I'm actually trying to figure out what that query is since sources of TagManager class implementation are not freely available and standard query debugging tools (logging querybuilder component) do not provide any insight

I have a requirement where AEM List component should return results based on Tag query with multiple tags using "any tag" search mode. It works just fine with 1-2 tags, but with eh tags amount increase (5-6 is normal in our circumstances) it sometimes take several minutes to return results. Our cont...

Direct links do not work but you may start browsing from the main page: https://docs.adobe.com/docs/en/aem/6-1/ref/widgets-api/index.html

Actually, I can't. We are sill on AEM 5.6.1 and what I mentioned above is a quote from Adobe response. IMHO the only way how to get it fixed is to keep pestering Adobe support :-)