Thanks kautuksahni for the valuable info. I've been using Apache
redirects in the dispatcher to add '/content' back on to the path so it
matches what is in the Publishers. But is seems from your post that this
can also be done using Sling OSGi configurations as well. Is there an
advantage to doing it one way over the other?
I'm having some issues upgrading 6.2 Servlets to 6.4. So I tried
uploading the WKND packages to see if the SimpleServlet is working:WKND
Packages location = Getting Started with AEM Sites - WKND Tutorial
Looking at the class annotations from the github repo :
* Servlet that writes some sample content into the r...
I want to cache authenticated content in the dispatcher for performance
and found this KB that shows a way to do it.Permission Sensitive Caching
Delivery Does anyone know if 6.x now support this out of the box, or do
we still have to write a customer servlet as this article shows?
From what I can tell, OSGi should support the ability to run two
versions of the same bundle. But I'm not able to do it either through
the Felix console or through package deployment.Does anyone have
experience doing this?
Following on Jörg Hoh's comment about building cacheable pages in the
dispatcher... I'd add that this has to be part of you design strategy.
There are some common web practices that will bust the dispatcher cache
if you are not careful. One example is urls with query strings params
which by default are not cached. You can configure the dispatcher to
blacklist params but that only helps if you know what params will be
added. However, most large scale commercial web sites will use things
For some reason our 6.2 Author instance is writing the error.log file to
the file system with rw ------ permissions. I've looked online but can't
seem to find a way to configure file permissions. the other log files
are OK. Anybody encounter this before ? -rw-r--r-- 1 40134 4160 322662
Dec 20 15:57 access.log-rw-r--r-- 1 40134 4160 1780254 Dec 15 19:08
access.log.2017-12-15-rw-r--r-- 1 40134 4160 132162 Dec 17 23:44
access.log.2017-12-17-rw-r--r-- 1 40134 4160 748052 Dec 18 23:59
My business users would like to start tagging their content at the
cq:Component level. Out of the box, AEM will let authors tag a Page or
an Asset, but I have not seen any components that do this. I know I
could create a custom cq:Component that would let the authors access
tags via the TagManager API, but I'm not sure it's a good idea to add
tags in the JCR in nodes other than Pages or Assets, given that AEM only
adds them to the cq:tags property in Pages and Assets. Wondering if
anyone has exp...