Seems like /crx/explorer/index.jsp;%0aa.css is blocked. But /bin/querybuilder.feed.css is not blocked. Can I get ideas on how to implement this?

Using the below configs, I was able to block /crx/de/index.jsp;%0aa.css and /bin/querybuilder.json.servlet;%0aa.css{ /type "deny" /url"/crx/*.css"}{ /type "deny" /url "/bin/querybuilder*.css"}But I am not able to block /crx/explorer/index.jsp;%0aa.css and /bin/querybuilder.feed.cssSo for blocking th...

Here is our config file.  # only handle the requests in the following acl. default is 'none'  # the glob pattern is matched against the first request line  /filter    {    # deny everything and allow specific entries    /0001 { /type "deny"  /glob "*" }      # open consoles  #    /0012 { /type "allo...

AMS has run a inspection on our dispatcher and asked us to block the below paths: should NOT respond to GET /bin/querybuilder.feed.css with 200should NOT respond to GET /bin/querybuilder.json.servlet;%0aa.css with 200should NOT respond to GET /crx/de/index.jsp;%0aa.css with 200should NOT respond to ...

Do you mean that this doesn't work for CRX?{ /type "deny"  /url"/crx/de/index.jsp;%0aa.css" }{ /type "deny"  /url"/crx/explorer/index.jsp;%0aa.css" }

I am trying to block these: should NOT respond to GET /bin/querybuilder.feed.css with 200should NOT respond to GET /bin/querybuilder.json.servlet;%0aa.css with 200should NOT respond to GET /crx/de/index.jsp;%0aa.css with 200should NOT respond to GET /crx/explorer/index.jsp;%0aa.css with 200so  does ...

As part of our environment Scan from AMSSEC suggested this to be fixed. "should NOT respond to GET /bin/querybuilder.feed.css with 200" In the scan it turned out to be Green, which AMS prefers it to be Red. How do I get this fixed?

Version Purge is working fine in other Environments but it is failing in QA, Does anyone know the reason for this and how to resolve it?14.02.2019 01:50:44.020 *ERROR* [sling-threadpool-7bf6ffa1-0d39-4356-a180-53818e4da83f-(apache-sling-job-thread-pool)-10604-Maintenance Queue(com/adobe/granite/main...

Hi Jorg,We have decide that they are Orphan because they have no property  attached to it. It is difficult to manually go through all the nodes and check which node has no property attached to it. We want to run a script which deletes the Orphan Nodes on a regular basis.

Is there a way that I can get the logic?