Interactions between multiple processors can 'break' URLs that are known to the
ResourceAuthorizationManager. This processor can be put as a post processor
following the other processors to 'fix' this.
Contains a basic unit test in core, and another in extensions that demonstrates
(and fixes) the negative behaviour of CssUrlRewritingProcessor and
Less4jProcessor interacting.
Reference:
Github pull request: https://github.com/alexo/wro4j/pull/185
Original issue reported on code.google.com by alex.obj...@gmail.com on 12 Jun 2014 at 1:17
Original issue reported on code.google.com by
alex.obj...@gmail.com
on 12 Jun 2014 at 1:17