Hello Jason,
The filter order was (due to a misunderstanding) aligned to the standard
interpretation of the service.ranking property, which indeed means that it
is inverted starting from Sling Engine 2.3.3 onwards. This change will *not*
be reverted in the future, as this would yield even more
Working on an upgrade to AEM 6.0sp2 and things started going weird all over the
place. Figured out the ordering of the servlet filters got reversed.
Per https://issues.apache.org/jira/browse/SLING-2920
We're now going through the process of changing our filter run ordering .
However I'm not
