Details

      Description

      1. Set the following portal property: layout.friendly.url.page.not.found=/web/guest/home
      2. Deploy the attached test-404-hook-7.0.0.1.war
      3. access http://localhost:8080/web/guest/home
        in the console you see the expected value: "responseStatus: 200"
      4. access http://localhost:8080/web/guest/home1
        in the console you see the UNEXPECTED value: "responseStatus: 200"

      If ETagFilter is turned off (com.liferay.portal.servlet.filters.etag.ETagFilter=true) or layout.friendly.url.page.not.found is not set, 404 is written to the log.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                linda.sui Linda Sui
                Reporter:
                akos.thurzo Akos Thurzo (Inactive)
                Participants of an Issue:
                Recent user:
                Esther Sanz
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Days since last comment:
                  5 years, 1 week, 6 days ago