Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-13771

Ensure AbsoluteRedirectsFilter is still the first filter when EXT plugins are deployed

    Details

    • Branch Version/s:
      6.0.x, 5.2.x, 5.1.x
    • Backported to Branch:
      Committed

      Description

      The ordering of the <filter-mapping> elements in web.xml determines the filter order in the filter chain.

      Unfortunately, ExtHotDeployListener invokes WebXMLBuilder in order to merge the web.xml, and WebXMLBuilder just puts everything in the EXT plugin's web.xml front of what's currently in Liferay's web.xml. This means all the filter-mapping elements in an EXT plugin will appear first, and so all the EXT filters will run before the Liferay ones.

      Seeing how much data is in web.xml, I don't see a good way for you to say "this filter should come after this other filter", but presumably, if there is a filter that we say in the documentation should come first, then it should come first even after we merge the XML and WebXMLBuilder should recognize that.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                support-lep@liferay.com SE Support
                Reporter:
                minhchau.dang Minhchau Dang
                Participants of an Issue:
                Recent user:
                Esther Sanz
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Days since last comment:
                  8 years, 50 weeks, 5 days ago

                  Packages

                  Version Package
                  6.1.0 CE RC1